2. FAQ: ES2016 and ES2017
2.1 Isn’t ECMAScript 2016 too small?
ES2016 being so small demonstrates that the new release process (as described in the previous chapter) works:
- New features are only included after they are completely ready and after there are at least two implementations that were sufficiently field-tested.
- Releases happen much more frequently (once a year) and can be more incremental.
ES2016 will give everyone (TC39, engine implementors, JS developers) time to catch their breath and is a welcome break after the enormous ES6 release.