ECMAScript 6, A Better JavaScript for the Ambient Web Era
summary
ECMAScript 6 claims to be feature complete and already lands in browsers incrementally, the draft is about 650 pages vs ES5.1’s 250, and major engines cut common benchmark times from seconds to ~100ms between 2008–2013 so performance is no longer the blocker. New concrete features include let and const with block scoping, the temporal dead zone rule for uninitialized bindings, and carefully designed block-function hoisting to preserve existing web compatibility.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:40The Ambient Computing Era
- 2:01Each Computing Era has had Canonical Programming Languages
- 2:20Why JavaScript? Because "Worse is Better"
- 5:07How Does JavaScript Evolve?
- 7:02JavaScript Early history
- 10:16What is ECMAScript?
- 13:36ECMAScript: Troubled Adolescence
- 17:15JavaScript Performance 2008 SunSpider (Vista SPI)
- 17:38JavaScript Performance 2013 SunSpider 1.0.2
- 18:05The ECMAScript Standard Timeline
- 26:38The closure-in-loop problem
- 28:04var hoisting causes the problem
- 28:50ES6 can't redefine the scoping of var
- 29:40Other local scoping WTFS
- 35:50Avoid inconsistent scoping WTFS //Forward or outer reference
- 37:52And bogus forward references
- 41:17Some ES6 Declaration Rules
- 42:25What about Block Scoped Functions?
- 43:50and real browsers, disagree...
- 45:05Unfortunately, all browsers agree
- 45:30What is the common interoperable browser semantics for block function declarations?
- 45:46Making block scoped functions compatible with intersection semantics
- 46:49ECMAScript Resources
related talks
01h 08mECMAScript 6: A Better JavaScript for the Ambient Computing Era
49mECMAScript 6, The Future of JavaScript
26mECMAScript 6 is so 2015! Meet ES2016
53mUsing ECMAScript 6 today. Part II
47mECMAScript: latest and upcoming features
43mWhat’s new in ES6 for Web Devs
41mUsing ECMAScript 6 today. Part I
21mWhat's ECMAScript 6 Good For?