11–20 of 93 posts
Good to see such quick progress in this area in major browsers. It's worth noting that WebKit also has 100% support for ES 2016+. So now only Edge is lagging in this regard. [0] http://kangax.github.io/compat-table/es2016plus/#webkit
It doesn't help when one needs to target enterprise markets or devices that only have their factory provided browser.
Good to see such quick progress in this area in major browsers. It's worth noting that WebKit also has 100% support for ES 2016+. So now only Edge is lagging in this regard. [0] http://kangax.github.io/compat-table/es2016plus/#webkit
Chrome has 85% in the above table (up from 80% from previous version), so why you are saying 100%? Maybe the above table doesn't include beta releases of Chrome?
Earlier quoted context omitted.
It doesn't help when one needs to target enterprise markets or devices that only have their factory provided browser.
That's what Babel[0] is for. Realistically you can't rely on native ES2016 for any target audience yet, but with Babel you can blissfully live in the future, today :) Also, thrown in core-js[1] while you're at it. [0] https://babeljs.io/ [1] https://github.com/zloirock/core-js
I can see that strict mode inside a function using default parameters should throw according to the spec ( https://tc39.github.io/ecma262/#sec-function-definitions-sta... ) but does anyone know why? Is strict mode something we should now be avoiding?
Earlier quoted context omitted.
It doesn't help when one needs to target enterprise markets or devices that only have their factory provided browser.
Of course it helps, only there is a bit of a lag. How many 'enterprise markets' run <IE9 nowadays?
I'd imagine that enterprises are still running many products with similar insane requirements, because they never get updates.
[0] http://www.vcaa.vic.edu.au/Pages/prep10/ondemand/index.aspx
Earlier quoted context omitted.
It doesn't help when one needs to target enterprise markets or devices that only have their factory provided browser.
Of course it helps, only there is a bit of a lag. How many 'enterprise markets' run <IE9 nowadays?
Good to see such quick progress in this area in major browsers. It's worth noting that WebKit also has 100% support for ES 2016+. So now only Edge is lagging in this regard. [0] http://kangax.github.io/compat-table/es2016plus/#webkit
Chrome has 85% in the above table (up from 80% from previous version), so why you are saying 100%? Maybe the above table doesn't include beta releases of Chrome?
Earlier quoted context omitted.
It doesn't help when one needs to target enterprise markets or devices that only have their factory provided browser.
That's what Babel[0] is for. Realistically you can't rely on native ES2016 for any target audience yet, but with Babel you can blissfully live in the future, today :) Also, thrown in core-js[1] while you're at it. [0] https://babeljs.io/ [1] https://github.com/zloirock/core-js
Some of our projects are with customers that still rely on XP with IE 8, require using the "Internet Browser" for pre-Android 4.4 or Windows Safari (!) or IoT devices without updatable browsers.
I can see that strict mode inside a function using default parameters should throw according to the spec ( https://tc39.github.io/ecma262/#sec-function-definitions-sta... ) but does anyone know why? Is strict mode something we should now be avoiding?
If you're using a bundler and transpiler, ES modules are already in strict mode.
Earlier quoted context omitted.
Chrome has 85% in the above table (up from 80% from previous version), so why you are saying 100%? Maybe the above table doesn't include beta releases of Chrome?
It's true, I forgot to mention Chrome which no longer uses WebKit.