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

WebKit is now 100% ES6 complete

twitter.com

Post reply on HN
Print view View original

31–40 of 119 posts

Re: WebKit is now 100% ES6 complete

#31

Post by g4k »

sotojuan wrote: post #24
liquidise wrote: post #17

Earlier quoted context omitted.

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.

I wish Safari would have the same incognito mode as Chrome's. Currently, tabs in the same incognito window do not share sessions so you have to log in again on every new tab.

I prefer it this way around. There is even a long standing issue in the Chromium bug tracker https://bugs.chromium.org/p/chromium/issues/detail?id=24690

Re: WebKit is now 100% ES6 complete

#32

Post by acbabis »

domenicd wrote: post #20
jasonellis wrote: post #11

Earlier quoted context omitted.

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

I'm confused by what it means that the semantics of imports weren't part of the spec yet. Do you mean polyfills like es6-module-loader (https://github.com/ModuleLoader/es6-module-loader) were just guessing how modules would behave?

Re: WebKit is now 100% ES6 complete

#33

Post by fooey »

anarchy8 wrote: post #25
fooey wrote: post #22

Earlier quoted context omitted.

And then, IE happens to your plans.

Ever heard of Babel?

If you're using Babel already, WebKit hitting 100% support is irrelevant. IE is going to be the thing that prevents us from running ES6 natively in the browser for several years more.

Re: WebKit is now 100% ES6 complete

#37

Post by t1amat »

hmottestad wrote: post #35

So, today I'm using babel to transpile my code to es5. Anyone know of any good tooling to use transpiled code for older browsers and es6 for newer?

What you are describing is serving up different assets based on user agent detection. The "tool" in this case would be the application responsible for serving it, most likely either your custom server-side web app code, or your web server itself.

You should continue to use the transpilers for some time though. It has been reported that many ES6 features run quite a bit faster as transpiled ES5 than natively as ES6.

Re: WebKit is now 100% ES6 complete

#39

Post by saidajigumi »

hmottestad wrote: post #35

So, today I'm using babel to transpile my code to es5. Anyone know of any good tooling to use transpiled code for older browsers and es6 for newer?

It'd be nice to see support similar to Autoprefixer[1]'s use of Browserlist queries[2]. Those let the developer to specify the desired target platforms by browser versions, by global usage stats (e.g. '> 5%'), or by custom usage stats ('> 5% in my stats') etc., and derive the correct prefixes needed to deploy to those targets.

EDIT (for clarity): It'd be great to see similar query support to derive a "lowest common denominator" Babel preset for an intended ES generation vs. browser profile set.

[1] https://github.com/postcss/autoprefixer [2] https://github.com/ai/browserslist#queries

Re: WebKit is now 100% ES6 complete

#40

Post by azinman2 »

nfriedly wrote: post #38

Note that this doesn't include ES6 modules. The referenced kangax compatibility table doesn't cover modules, so the tweet is technically correct, but the headline here on HN is a bit misleading.

They're in JavascriptCore, just not yet integrated into WebCore fully.

https://bugs.webkit.org/show_bug.cgi?id=147340

Post reply on HN