4 ms·
Well, JavaScript slowed down after ES2015 too. On the other hand, the module system really takes time and async/await was one big step.
by k__ 9y ago
Well, JavaScript slowed down after ES2015 too.
On the other hand, the module system really takes time and async/await was one big step.
- Klathmon 9y agoI disagree! After ES2015 includes: * Async/await * a bunch of destructuring with the rest and spread operators * More class "nice to haves" like static properties and possibly more soon * Async iteration * Shared memory and atomics (which I'm not all that happy about, but many people are) And going even further "in the future" it might have stuff like: * Decorators (of they can ever settle on it!) * Observables * Defensible classes (again, not really happy with this, but what can ya do!) * Function bind syntax * Some "collection" nice to haves And more. JS isn't going to be slowing down any time soon!
- parthdesai 9y agoIMO, async/await itself makes it worth upgrading to ES6. So much cleaner.
- Klathmon 9y agoAgreed, but Async/await is ES2017!
- k__ 9y agoI was talking about the standardization. Sure there is a bunch of proposals, but after ES2015 only a few per year are included.
- WorldMaker 9y agoES2015 rolled up around five/six years worth of changes since ES5 (which we could call ES2009, I suppose), so of course it's going to feel like it standardized a bunch more stuff. The new system is faster as annual releases, even if it seems like ES2016, and ES2017, seem "light" relative to previous standards.