Back to the future of JS: the next features and amazing proposals
summary
Shows concrete syntax and tradeoffs: a bind operator (::) fixes unpredictable this for event handlers without manual .bind or arrow wrappers; two pipeline designs compare a smart pipeline with placeholder token (#) and an F#-style |> that handles async/await differently; partial application adds argument placeholders like ? and ... to produce smaller-arity functions; pattern matching introduces match/case with guards and catch-alls. Proposals sit in early TC39 stages and are not yet production-ready.
AI-written summary · about
chapters (23)
- 0:00Start
- 3:20How to make this predictable?
- 4:28Calling a knowing function
- 5:12Extracting a method from an object
- 5:50Two syntaxes
- 6:05Unary syntax
- 10:14Function with more params
- 10:47Awaiting a function
- 11:45Smart pipeline
- 12:35What about curry?
- 12:57F# pipeline proposal
- 15:45Partial application in ES
- 16:51What about currying?
- 18:02Partial application proposal
- 18:26Partial application syntax
- 18:57With arbitrary parameter
- 19:11Partial application in template string
- 20:32Partial application + pipeline
- 21:08Conditionals in JS
- 22:39Switch Statement
- 24:57Ternary expressions
- 26:21Toy example
- 29:52Should I use all of it in production?
related talks
29mBack to the future of JS: the next features and amazing proposals
39mBack to the future of JS the next features and amazing proposals
25mBack to the future of JS II: Beyond what we can foresee
26mBack to the Future of JS II
11mWhat's cooking for JavaScript: a look at current TC39 proposals
25mFuture JavaScript: what is still missing?
33mESNext: Proposals to look forward to
53mUsing ECMAScript 6 today. Part II