Does this include native module import/export? I never saw anything to suggest they were even working on that.
Module import/export syntax was in ES6, but the browser implementation has not yet been standardized.
WebKit is now 100% ES6 complete
11–20 of 119 posts
Re: WebKit is now 100% ES6 complete
#12Heh, after I saw it was 96-7% last time (when the developer preview versions were announced), I was pretty sure they'd push it to 100% soon, to make a (small) point of it on the WWDC Keynote.
Re: WebKit is now 100% ES6 complete
#13Is anyone using Safari Technical Preview as their main Browser? I was hesitant to use it, but I've heard a few people say that it's stable.
Re: WebKit is now 100% ES6 complete
#14100% ES6 complete ...and abandoned in Qt5, since recently :(
Re: WebKit is now 100% ES6 complete
#15Is ES6 native much faster than transpiled?
From my limited anecdotal testing no. In fact it may be slower. This is a good view of this: https://kpdecker.github.io/six-speed/ However... the potential upside is size. Native code will usually be smaller, which for a web client is a win.
I'm having trouble reading the table, when it says 16x slower, is it saying the implementation is slower or the engine?
Re: WebKit is now 100% ES6 complete
#16Is anyone using Safari Technical Preview as their main Browser? I was hesitant to use it, but I've heard a few people say that it's stable.
I did use the 1st release on a daily basis, but I had some problems with it (few websites misbehaved). I may revisit it since it's already at its 4th release and they fixed a ton of bugs judging from their release notes.
Re: WebKit is now 100% ES6 complete
#17Is anyone using Safari Technical Preview as their main Browser? I was hesitant to use it, but I've heard a few people say that it's stable.
I tried for about a week. My complaints with it were the same i have with base Safari, but TP specifically worked fine. No unique issues despite using it as dev platform and a consumer browser.
Re: WebKit is now 100% ES6 complete
#18Watching that table makes me think it's about time to start switching to es6
Re: WebKit is now 100% ES6 complete
#19Webkit was probably one of the last major web engines to start integrating ES6 features, yet they have TCOs done. Anyone explain what's holding it up in Chrome/FF/Edge?
Re: WebKit is now 100% ES6 complete
#20Does this include native module import/export? I never saw anything to suggest they were even working on that.
Module import/export syntax was in ES6, but the browser implementation has not yet been standardized.
Well, it's been standardized, but implementation work is still ongoing. Details at https://blog.whatwg.org/js-modules