Frontend-centered Development: the Future of Web Development
summary
Traces three real projects and the concrete tradeoffs: Drip — Ruby on Rails + jQuery ships fast but accumulates duplicated templates and spaghetti JavaScript; Level — Elixir + GraphQL + Elm delivers snappy single‑page UX and strong types but suffers bundle growth and a small ecosystem; StaticKit moves to Next.js with static export and server-side rendering to get meaningful first renders, built-in prefetching, faster developer productivity, and fewer manual optimizations.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:50About Derrick
- 2:00Lots of progress
- 2:25Technology choices
- 3:38Life on the bleeding edge
- 4:10Drip
- 4:25Special Considerations
- 4:47Rails and jQuery
- 5:23No technology stack is perfect
- 7:25Level
- 7:43Considerations
- 8:07Elm
- 9:10Benefits
- 10:13Drawbacks
- 11:58StaticKid
- 12:27Serverless
- 13:22Elixir
- 15:06Benefits of Next
- 16:51Concrete Example
- 17:43Universal JavaScript
- 18:28Contextual Documentation
- 19:22Final Observations
related talks
40mFRONTEND CHOICES
38mThe Front-End Future
32mWhat's Happening in the JavaScript Ecosystem?
29mQuo vadis, frontend?
23mPros Do Vanilla - A Loosely Coupled Front-End
01h 10mThe Future of Frontend Panel
58mAlways crashing in the same car (the state of front end web development in 2022)
49mFront Ends for Back End Developers