Nicolas Zakas interviewed at Velocity 2011

on YouTube ↗05m

" summary

JavaScript grows from misunderstood toy to practical platform with concrete advice: start optimization by measure first—benchmark to see whether time is lost in JS, resource count, or bytes over the wire. Defines time to interactivity as the time from URL enter to task completion and urges deferring nonessential JS so pages don’t freeze. Notes Node on server revives Netscape’s original idea, predicts mainstream adoption in a few years, and cites desktop packaging (Adobe AIR and others) as evidence of an emergent HTML/CSS/JS stack.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 0:10Are You Surprised at Javascript's Current Position
3. 0:41Why Why Does Javascript Become So Important to You
4. 1:09Beginning Optimization Efforts
5. 1:23Performance Optimization
6. 1:43What Is Time to Interactivity
7. 2:39Take on Node

" related talks

• 48mJavaScript in Browser PerformanceSteve Souders · JSConf.eu 2009
• 41mJavaScript, Day 4001Illya Klymov · JavaScript fwdays'18
• 38mJavascript Considered...UsefulJenn Schiffer · JSConf EU 2019
• 34mUnderstanding JavaScript PerformanceGodfrey Chan · EmberConf 2017
• 11mRevolutionizing JavaScript PerformanceDeepika Annam · Conf42 JavaScript 2025
• 52mOverboard.jsChristian Heilmann · JSConf.Asia 2015
• 44mAdvancing the web without breaking it?Christian Heilmann · beyond tellerrand Düsseldorf 2015
• 31mThe Future of Front-End PerformanceSia Karamalegos · Full Stack Fest 2018