3 ms·
> One because they didn’t want to update their JS engine and the other had just released v8. ECMAScript 4 was canceled for a whole host of reasons. Trying to b
by klodolph 4y ago
> One because they didn’t want to update their JS engine and the other had just released v8.
ECMAScript 4 was canceled for a whole host of reasons. Trying to blame browser vendors is just bonkers. The standard made too many changes all at once and existing work on implementations had progressed too far.
https://auth0.com/blog/the-real-story-behind-es4/ https://auth0.com/blog/the-real-story-behind-es4/
- jmisavage 4y agoI wouldn’t say its bonkers at all. That’s a good blog post not trying to lay a ton of blame on any one person. But having worked with Macromedia/Adobe and Mozilla engineers at the time who already successfully implemented a majority of the spec they were quite frustrated with everyone else looking for ways to slow things down or stop it wholesale. We can’t change the past. Unfortunately we are reinventing a lot of what was done in that early work, but now with some strange syntax because of compatibility with dead features or 3rd party libraries that picked up the slack. At least we finally have a standard for importing packages…again.