The (now and the) future of JavaScript
David Lorenz | info@activenode.de | https://github.com/activenode | @activenodeio
web enthusiast | full-stack developer
#javascript #es2016 #es2017 #futureofjs #webdevbbq
or: not another ES6/ES7 talk
First things first:
After ES6 (2015) lifecycle had to be reduced.
-
ES6 = ES2015
-
ES7 = ES2016
-
ES2017
-
ES2018
-
...
First things first:
Versions don't matter!
The ES2016, ES2017, etc. version is important to the ES contributors
(here you find the Task Force: http://www.ecma-international.org/memento/TC39.htm).
But why do you care?
First things first:
Versions don't matter!
Once you know that a feature will be implemented because it already reached stage 3: use it when transpile-able.
The process each feature has to go through: https://tc39.github.io/process-document/
The stages of a JS feature:
- Strawman
- Proposal
- Draft
- Candidate
- Finished
When Object.observe was removed
Blame yourselves: Object.observe did only reach stage 2.
This presentation is about features!
Not versions.
Agenda
There is so much, I can only extract
a few features from ESX
Want a list? Better go coding right now.
Get smart
- https://www.youtube.com/watch?v=3pKNRgResq0
- https://leanpub.com/exploring-es2016-es2017/read
- http://exploringjs.com/es6/
- http://esnextnews.com/
- https://babeljs.io/
The future of JavaScript: ES6, ES7 and forth
By activenode
