On Fri, Jul 21, 2017 at 9:37 PM, kai zhu <[email protected]> wrote:
> that being said, es6 is such a different beast from es5, that i > think a backwards-compatible “use es5” text pragma would be > appreciated by the significant number of veteran frontend- > programmers and established companies who still prefer > writing and maintaining code in the “legacy” language-style Can you produce any data at all to back that up? I've never seen any appetite in that regard at all. You do realize, presumably, that there is *nothing* preventing you from writing ES5 code and running it on current engines -- since ES2015, ES2016, and ES2017 are all backward-compatible with ES5. By design. Don't like `const`? Don't use it. Don't like arrow functions? Don't use them. Don't like `async`/`await`? (You guessed it.) Don't use them. Nothing other than unspecified behavior is any different unless you use it. (And even in regard to unspecified behavior [I'm thinking function declarations in blocks here], the committee has bent over backward to do their best to avoid imposing changes on it.) -- T.J. Crowder
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
