ES6 vs libraries

From: CHYRON (DSMITHHFX)28 Sep 2018 12:07
To: Peter (BOUGHTONP) 3 of 5
Combined Oral Contraceptives? Canadian Opera Company?
From: Matt 1 Oct 2018 17:47
To: CHYRON (DSMITHHFX) 4 of 5
ES6 (ES2015) is JavaScript (technically, JavaScript is an implementation of EcmaScript) and it's already here.

There is also ES2016 (ES7), ES2017 (ES8) and ES2019 (ES9) all of which contain forthcoming features for JavaScript to implement.

Don't confuse ES6 with the removal of frameworks/libraries, it doesn't do away with them nor forbid them. It's rai·son d'ê·tre is to improve JavaScript to add functionality like document.querySelector that allow you to accomplish jQuery-like functionality without importing the entirety of jQuery, but there are still plenty of things that ES6 cannot do that jQuery can (more easily). To be clear, there is nothing stopping jQuery from still existing and making use of ES6 features if it wants to.

To summarise, ES6 is an evolution of JavaScript, not something to replace all your libraries.
 
Quote: 
Yeah, it has those pointy (=>) things.
These are called arrow-functions and they are awesome.
EDITED: 1 Oct 2018 23:33 by MATT
From: CHYRON (DSMITHHFX) 1 Oct 2018 20:14
To: Matt 5 of 5
Yeah, I'm slowly getting my head around some of the features. And the unrelated do's and dont's of service workers. Like SWs don't do DOM stuff, and sw "modules" are sandboxed to hell (because security?).