Our web development workflow is completely broken
summary
Claim: the front-end workflow is broken because editors and runtimes are disconnected, producing a daily reload-edit-repeat loop patched by extra tools. Evidence: layers of precompilers, file watchers and LiveReload use a websocket + cache-busting query hack rather than a real runtime API. Proposal and demo: reuse the Chrome Remote Debugging protocol as a common bridge (remote-debug.org) to let DevTools, Brackets, Sublime, etc. talk to Firefox, Chrome and phone runtimes so edits sync instantly.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:28Flashback
- 2:15Our web development workflow
- 3:35Todays web platform
- 3:56Application Runtime
- 8:05Our workflow
- 9:29Fixing the workflow
- 11:25New prototyping tools
- 12:14Chrome dev tools
- 13:18What does this mean
- 13:49Our assumptions are wrong
- 14:54Disconnect
- 15:23Keeping our editors
- 16:57Whats actually happening
- 18:01Remote debugging protocols
- 18:43Browsers have their own protocols
- 19:53Remote Debugging Talk
- 21:09Reusing Remote Debugging
- 21:57Hacking Remote Debugging
- 27:00What do you think
