proposal-do-expressions VS ECMAScript 6 compatibility table

> no pattern matching/switch expressions

They're still waiting on the do expression proposal for that (https://github.com/tc39/proposal-do-expressions), which has been in the bikeshedding stage for the past five years.

At some point, it may be superseded by do blocks, but for now it's really your best bet.

But there is a proposal for do-expression : https://github.com/tc39/proposal-do-expressions

It's also the reason why do expressions are my most anticipated feature for JS.

> They should repurpose `do` so that `do {}` (without the `while`) is an expression that you can put statements inside and return the last statement.

There's a proposal for precisely that. Unfortunately, only Stage 1 though.

https://github.com/tc39/proposal-do-expressions

It's one of the main reasons why I really want the do-expression propsal to work out, because then it would become:

Do blocks. Okay, this is actually a proposal so maybe someday. Basically blocks that can resolve to an expression.

Tomorrow, do expressions:

http://kangax.github.io/compat-table/es6/

This page lists features from es6 (and newer versions linked at the top) along with compliance to the spec. First column is the current browser, second is babel+corejs polyfills.

Overall, babel gets about 70% of the way there.

Case in point: Tail Call Optimization has been part of the JS spec since ES6, but remains completely unimplemented in all mainstream browsers/engines besides Safari[1]. For all but the most predictable inputs, you're pretty much forced to use loops where recursion would otherwise be preferable.

Additional case in point: async Iterables cannot be processed as a piped stream. You must use the for await construct, which is a shame considering the FP niceties that the Array type already provides for more traditional lists. Once again, you are forced to use an imperative construct unless you specifically want to defeat the purpose of using an Iterable in the first place by trying to convert it into an Array (... and potentially choking in the process, I might add!).

[1]: https://kangax.github.io/compat-table/es6/

Eventually the browsers started racing to near-full ES6 compatibility. I remember following ES6 progress in realtime with articles and with compatibility tables http://kangax.github.io/compat-table/es6/ . But many people are acting like that either didn't happen, or like it was a one and done thing (despite the ESNext naming shift to avoid the focus on numbers). So we see people just hand-waving away the importance of polyfills like in this gem:

> https://kangax.github.io/compat-table/es6/

Oh man this was a rough one both for FF and Chrome but Chrome did perform better slightly on cursory glance.

Thanks for providing these links, they're definitely a good rule of thumb benchmarks to test new browsers

Javascript / CSS language syntax: can see availability for Javascript here - https://kangax.github.io/compat-table/es6/

I say this as a JS user, but there is no singular JavaScript (realistically, it's not even JavaScript but instead ECMAScript). There is no one place to go that lays out all of what the language can or can't do the way PHP and Python do. The ECMAScript board makes recommendations, then the browsers and runtimes implement features of the recommendations. This site does a good job laying out which features are implemented for browsers and runtimes based on the flavor of the ECMAScript standard. This unique experience can be especially frustrating for someone learning JavaScript and coming from another language that does not have this problem.

https://kangax.github.io/compat-table/es6/ has a column for "current browser"