Milk lasts longer than some Javascript frameworks
summary
Builds a working "movies-that-fit-your-train-ride" app from scratch using only plain JavaScript, SystemJS loader, web components (custom elements + shadow DOM), ES6 modules and the fetch API to call a movies service and Google Maps for trip duration. Implements a simple router by hand, admits that becomes "a tiny framework", and demos real results (three movies for Basel–Bern). Argues for learning concepts and standards instead of chasing a new framework every 18 months.
AI-written summary · about
chapters (22)
- 0:00Introduction with questions
- 1:33Experiment setup and goals
- 2:15Speaker introductions
- 3:19Problem statement and app idea
- 4:21Starting with custom elements
- 6:31Live coding begins
- 7:16Building the movie tile component
- 9:50Creating the movie view component
- 11:55Organizing with ES6 modules
- 15:03Fetching real movie data
- 18:46Implementing search view
- 20:12Adding event handling
- 22:29Introducing HTML routing
- 23:52Building the router view
- 25:59Implementing the router
- 27:48Connecting search to results
- 28:33Reviewing the final app
- 28:53Good parts of the approach
- 29:15Bad and ugly parts
- 30:38Four key lessons learned
- 33:24Sustainable knowledge tips
- 33:45Q&A session
related talks
45mNo framework frontends in practice - use the platform!
41mThe future is modules not frameworks. JS modules Architecture demo.
22mThe vanilla way
31mGetting up to Speed with JS Today
37mMeteor - A Full Stack Framework For Building Pure JavaScript Apps
44mJavaScript in 2017: You might (not) need a framework
32mModern JavaScript, without giving up on Rails Jonathan Johnson
23mParty like it's 1999, write JavaScript like it's 2012