Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ECMAScript 2016+ in Firefox

blog.mozilla.org

Post reply on HN
Print view View original

1–10 of 93 posts

Re: ECMAScript 2016+ in Firefox

#4

Post by pjmlp »

M4v3R wrote: post #2

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.

Re: ECMAScript 2016+ in Firefox

#5

Post by Touche »

pjmlp wrote: post #4
M4v3R wrote: post #2

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.

Nope, not everything is for everyone.

Re: ECMAScript 2016+ in Firefox

#6

Post by diggan »

nailer wrote: post #3

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?

According to the documentation on MDN[0], it's a part of "early errors" and you should rather but the "use strict" outside the function instead of on the inside. I'm not entirely sure of why the spec wants it to be outside rather than inside though...

- [0] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Re: ECMAScript 2016+ in Firefox

#7

Post by swhipple »

nailer wrote: post #3

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?

See here [1], under "Why make this change?".

[1] https://www.nczonline.net/blog/2016/10/the-ecmascript-2016-c...

Re: ECMAScript 2016+ in Firefox

#8

Post by paol »

pjmlp wrote: post #4
M4v3R wrote: post #2

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.

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

Re: ECMAScript 2016+ in Firefox

#9

Post by krzyk »

M4v3R wrote: post #2

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?

Re: ECMAScript 2016+ in Firefox

#10

Post by bushin »

nailer wrote: post #3

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?

Nicholas Zakas has a nice explanation

https://leanpub.com/understandinges6/read#leanpub-auto-chang...

Post reply on HN