Web Panel
summary
Panel gives concrete takeaways: the web’s user wait is still ~80% front end, the current bottleneck is CPU mostly from JavaScript, and real pages commonly load 2 MB of JavaScript. Practical tools and practices called out include long tasks API (Chrome), Visual Studio Code, Prettier, WebPageTest/WhySlow, and using the TypeScript compiler for static checks. Warnings: async/await can serialize parallel work, classes add complexity, and tail call optimization remains missing — measure, benchmark whole apps, and start simple.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 2:00New exciting features
- 2:50The bad things
- 4:30The editing experience
- 5:15Visual Studio Code
- 8:15JavaScript performance
- 9:35Libraries and frameworks
- 11:40Building effective teams
- 14:05Measuring performance
- 15:35Bringing your team along
- 16:55New features
- 19:55Classes
- 21:10Async and await
- 22:35Performance vs functionality
- 23:05Mike North on performance
- 23:55Douglas Crockford on performance
- 32:20Douglas Crockford on the need for a traditional degree
- 35:10Steve Souders on the need for deeper education
- 37:05Doug Crockford on interviewing engineers
- 39:25Steve Souders on interviewing engineers
- 40:55Biggest fear for the web
- 42:45How to manage code complexity
- 44:55Is there anything scary in es6
- 47:02Is JavaScript harder than ever
- 48:25Thoughts on JavaScript
- 50:05Solutions
- 53:07Conclusion
- 55:02Thank you
related talks
41mPanel: Web
44mWeb Components Can't Save Us. But You Can!
24mSuperpowers of browser's Web API
27mHow we make Web Apps lightning fast at Microsoft
24mThe Good, The Bad, and The Web Components
35mWeb Application Performance Testing from Users Perspective
48mJavaScript in Browser Performance
38mDear Developer, the Web Isn't About You