5 ms·

I wonder if ES6+ is going to become the new HTML5 - all these great features but no hope of proper browser support for years. I had no idea ES7 was also in deve

I wonder if ES6+ is going to become the new HTML5 - all these great features but no hope of proper browser support for years. I had no idea ES7 was also in development, so it seems like browsers are always going to be playing catchup. The comments on an article here the other day said people aren't upgrading tablets as often as phones. I can see a lot of tablets being stuck on ES5, that people don't want to upgrade, as they can still browse the Facebooks and Googles fine.

mbrubeck 12y ago
Firefox and IE11 already natively implement a majority of new ES6 features, and Chrome is getting there: http://kangax.github.io/compat-table/es6/ http://kangax.github.io/compat-table/es6/ The main laggard for now is Safari/WebKit.
- TheHippo 12y ago
  Current stable browser versions: FF 35: 60% Chrome 40: 35% Safari 8/Mobile: 22% IE11: 21%
  - mbrubeck 12y ago
    Oops, yeah. I wrote "IE11" but I meant "IE TP". The dev versions of IE/Firefox/Chrome/WebKit are up to 70%/69%/48%/28% respectively.
- pjmlp 12y ago
  > Chrome is getting there They are busy with that other programming language.
underwater 12y ago
Most of the JavaScript community is already using this, thanks to tools like https://6to5.org/ https://6to5.org/. Developers are excited about new language features not because of browser support, but because it standardizes patterns they were already using (fat arrow functions, Promises, modules, classes, etc.) through CoffeeScript and third-party code.
- bshimmin 12y ago
  I think your "most" is rather optimistic. (6to5 didn't even exist six months ago.)
steveax 12y ago
And the beauty of using ES6 is when the browsers you need to support handle, you just remove the transpiling step.
- CmonDev 12y ago
  How much of this beauty will be fixed in ES6? http://wtfjs.com http://wtfjs.com
  - nawitus 12y ago
    Some of those problems are with the DOM and browsers, not JavaScript.
    - CmonDev 12y ago
      True, there are numerous issues with each and every aspect of client-side web development: http://wtfhtmlcss.com http://wtfhtmlcss.com
  - quadratini 12y ago
    Bad code leads to inconsistent behavior. Who would have thought.

mbrubeck 12y ago

Firefox and IE11 already natively implement a majority of new ES6 features, and Chrome is getting there: http://kangax.github.io/compat-table/es6/ http://kangax.github.io/compat-table/es6/ The main laggard for now is Safari/WebKit.

TheHippo 12y ago
Current stable browser versions: FF 35: 60% Chrome 40: 35% Safari 8/Mobile: 22% IE11: 21%
- mbrubeck 12y ago
  Oops, yeah. I wrote "IE11" but I meant "IE TP". The dev versions of IE/Firefox/Chrome/WebKit are up to 70%/69%/48%/28% respectively.
pjmlp 12y ago
> Chrome is getting there They are busy with that other programming language.

underwater 12y ago

Most of the JavaScript community is already using this, thanks to tools like https://6to5.org/ https://6to5.org/. Developers are excited about new language features not because of browser support, but because it standardizes patterns they were already using (fat arrow functions, Promises, modules, classes, etc.) through CoffeeScript and third-party code.

bshimmin 12y ago
I think your "most" is rather optimistic. (6to5 didn't even exist six months ago.)

steveax 12y ago

And the beauty of using ES6 is when the browsers you need to support handle, you just remove the transpiling step.

CmonDev 12y ago
How much of this beauty will be fixed in ES6? http://wtfjs.com http://wtfjs.com
- nawitus 12y ago
  Some of those problems are with the DOM and browsers, not JavaScript.
  - CmonDev 12y ago
    True, there are numerous issues with each and every aspect of client-side web development: http://wtfhtmlcss.com http://wtfhtmlcss.com
- quadratini 12y ago
  Bad code leads to inconsistent behavior. Who would have thought.