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

JSC loves ES6

webkit.org

Post reply on HN
Print view View original

111–120 of 191 posts

Re: JSC loves ES6

#111

Post by jfbastien »

pizlonator wrote: post #78
bla2 wrote: post #75

Earlier quoted context omitted.

That's cool, but it feels a bit like making sure your room is tidied up while your house is on fire -- it's not clear it's the most pressing priority. But webrtc support is cool.

My house is definitely not on fire. That much I can tell you. My room, on the other hand, is definitely not tidy. Haven't cleaned that shit in ages.

Your office is pretty tidy though.

But seriously, we have a bunch of developers asking for JavaScript improvements. Maybe OP doesn't want them, fine that's useful feedback... but it would be more easily received if it came in a nicer package :)

Re: JSC loves ES6

#112

Post by donjoe »

millstone wrote: post #100
reitanqild wrote: post #96

Earlier quoted context omitted.

To serve that requests from local storage if your device or the server is offline.

If the asset is already in local storage, why do you need to create a network request in the first place?

...since you don't know whether there is a new version available on the server or not. To not make the user wait, you show him/her the - potentially - outdated version of your data until a new version is available. It's especially useful in situations where users lack internet connection.

Re: JSC loves ES6

#113

Post by jfbastien »

hoodoof wrote: post #82
jfbastien wrote: post #29

Earlier quoted context omitted.

I think OP meant 2015 is two years ago, claiming it makes it look behind. Truth is, ES6 is what we've called it, ES2015 is to confusing cool new name!

>> ES6 is what we've called it, Who is "we"?

The WebKit team.

You like that question! Third time in this thread already

Re: JSC loves ES6

#114

Post by xenadu02 »

zachrose wrote: post #104
millstone wrote: post #100

Earlier quoted context omitted.

If the asset is already in local storage, why do you need to create a network request in the first place?

Or why can't this problem be solved with HTTP caching headers and a browser that Does the Right Thing?

So HN commenters who don't use Service Workers can have some invective to throw at WebKit.

Re: JSC loves ES6

#115

Post by chuckdries »

emsal wrote: post #14
k__ wrote: post #9

Earlier quoted context omitted.

Doesn't Electrino basically try this?

Currently it looks like Electrino only supports macOS. Doesn't it sort of defeat one of the purposes of using a web-based framework for desktop apps if it's not even cross-platform?

I mean, the difference between rewriting an app and tweaking to compile on a different toolkit is not trivial, but I see your point

Re: JSC loves ES6

#116

Post by alwillis »

justabystander wrote: post #67
pizlonator wrote: post #44

Earlier quoted context omitted.

That shows WebKit supporting tailcalls. It doesn’t a show Chrome supporting tail calls. I vividly remember us implementing tail calls and v8 not having them yet at that time. This was almost 2 years ago.

Chrome has had them for a while. Supposedly they just hid them behind a flag because they weren't satisfied with some perceived deficiencies in the spec. (Check out https://v8project.blogspot.com/2016/04/es6-es7-and-beyond.ht... ) WebKit did have it somewhere between mid-October to early December of 2015. ( http://web.archive.org/web/20151207203829/http://kangax.gith... ) Chrome didn't get it until late April of the…

I'm still grudging at Apple for the year's delay between Safari 9 and 10, which left all the clueless Apple customers on ~53% ES6.

But Apple got to 100% ES6 support before anyone else: https://twitter.com/webkit/status/728643624464883712?lang=en

Re: JSC loves ES6

#117

Post by saamyjoon »

deecewan wrote: post #57
pizlonator wrote: post #47

Earlier quoted context omitted.

Chrome and WebKit are two different things. So, no, you didn’t just say that.

He said that chrome and Firefox had everything except for tail call optimisation earlier.

FWIW, I don’t think this is accurate (not that it really matters much anymore). All the browsers were in the 90+% support around the same time.

Re: JSC loves ES6

#118

Post by untog »

shuckles wrote: post #105
rictic wrote: post #90

Earlier quoted context omitted.

http://caniuse.com/#feat=push-api is the interesting notifications API, which allows notifying a user (with their permission) even when the app isn't open. Neither API is supported on iOS Safari, and desktop Safari only supports notifications while the app is open.

“push notifications can reach your users regardless of whether your website or Safari is open“ https://developer.apple.com/library/content/documentation/Ne...

Not on iOS, and not the web standard everyone else uses.

If the only possible market is desktop Safari users then it's usually a rounding error not worth the development time.

Re: JSC loves ES6

#119

Post by untog »

emsal wrote: post #14
k__ wrote: post #9

Earlier quoted context omitted.

Doesn't Electrino basically try this?

Currently it looks like Electrino only supports macOS. Doesn't it sort of defeat one of the purposes of using a web-based framework for desktop apps if it's not even cross-platform?

It's still web based. You can just use one wrapper for one platform and one for another. A little extra effort, but if the engine makes it worth it then why not?

Re: JSC loves ES6

#120

Post by rizalp »

kccqzy wrote: post #18
pizlonator wrote: post #13

Earlier quoted context omitted.

Dunno about zero. Sounds hard.

I think what OP means is that instead of bundling a copy of Chromium, just use the system-provided WebKit and JSC, which is already loaded into memory.

But Windows and Linux doesn't have Webkit by default
Post reply on HN