3 ms·
> That's a bold statement. Why EcmaScript 5 and not JavaScript 1.4 for that matter? Because most devices will run most of ES5, very few devices will run any ES
by spriggan3 10y ago
> That's a bold statement. Why EcmaScript 5 and not JavaScript 1.4 for that matter?
Because most devices will run most of ES5, very few devices will run any ES6.
Now there are transpilers sure, but I remember a time Javascript was about simplicity and not relying on a complex grunt pipeline + Babel. Now JS tooling is more complicated than Java's only with JSON in place of XML. The irony.
- lucasmullens 10y agoI think for most people the time you save using ES6 features is more than the time it takes to set up a build system, at least for larger projects.
- alistproducer2 10y agoI would have to disagree. There's no way saving a few keystrokes on an arrow function or being able to use 'class' will ever compare to understanding, let alone debugging, gulp streams. IMO JS tooling has gone way overboard, but in code, as in any artform, everything is subjective.