Echo JS 0.11.0

<~>
ndks 3115 days ago. link 0 point ▲ ▼
I'm so annoyed by Microsoft touting their leading the edge of ES6 feature support. Especially with statements such as:

> last week’s Windows Insider Preview build 14342 brings more ES6 capabilities including modules, default parameters, and destructuring

With the exception of modules, Chrome and FF have supported the more frequently used ES2015 features like destructuring and default params for quite a while now.

Replies

gotofritz 3114 days ago. link -3 points ▲ ▼
I don't understand your point. They didn't claim to be first, or best. Just that Edge now supports more ES6 capabilities. Which is a fact. I think we should be glad now that MS seems to be doing the right thing, as opposed to certain other browser manufacturers who seem to have stopped caring.
tracker1 3112 days ago. link 1 point ▲ ▼
I'm not sure who you're referring to... Safari TP seems to have full ES2015 including modules, Chrome is ES2015 feature complete aside from modules and tail call opt.  They're pretty much all over 90%, or very close to feature complete within a release target of about 3 months.

That said, It'll take a little time for older browsers to fall off (IE and Safari being the boat anchors), so we'll be stuck with babel+webpack for a while.  All of that said, it will be nice to be able to have a build target that doesn't need regenerator or large shim libraries.