12 ms·

I wonder does ECMAScript 2017 has optional name ES8?

• mstade 10y ago
  Not really, but there's certainly an off-by-one joke in there somewhere. Since ES2015 the official nomenclature is ES<year>, to convey that a new version of the standard is cut yearly. While this may result in somewhat underwhelming releases, like ES2016, at least it's much easier to reason about and target than previously. Case in point, it took ten years or so to get from ES3 to ES5, and another five-six years I believe to get to ES2015. These were substantial releases to be sure, but for a long time the uncertainty about when a spec draft was considered done was anything but fun, and I for one applaud the new nomenclature and process for being much, much easier to reason about and target.
  • jakub_g 10y ago
    We must stop using names like ES8 etc. right now, otherwise there'll be a lot of confusion in 4024 about which version of ES your customers' IE supports.
    • u02sgb 10y ago
      Surely we'll get there in 2020 or 2021, is that ES10, ES11 or ES20, ES21? Edit: and yes I know you were joking :)