JSC loves ES6

Post by [deleted] » Tue, Jun 06, 2017, 9:58 AM UTC

lilbobbytables wrote: post #123

donjoe wrote: post #112

Earlier quoted context omitted.

...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.

I'm interested in this as well, as I haven't dove into service workers. But I'm still failing to see why you can't pull the local data from local storage and show it, then render the data from the server (should you get new data)?

Post by pfooti » Tue, Jun 06, 2017, 10:07 AM UTC

zajd wrote: post #48

pfooti wrote: post #33

It seems weird to focus so much on es2015 features, when so many of them are polyfillable (not optimal, sure, but still) when there is such uneven support for DOM (and related browser) API features in safari. I mean, where are service workers? Give me a nice, cross-platform way to handle offline-first and I'll be happy. But hey, it isn't like there's some kind of browser monopoly on iOS or anything, like there was in…

I'm pretty sure Safari's features are intentionally crippled to keep their app ecosystem safe. See: web notifications.

Post by cormacrelf » Tue, Jun 06, 2017, 1:12 PM UTC

cormacrelf wrote: post #109

zachrose wrote: post #104

Earlier quoted context omitted.

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

I'm pretty sure HTTP caching headers don't provide a guarantee that they will be stored for any length of time at all, the browser is free to empty it at will. They also don't guarantee that all your cached assets will be valid with respect to each other (ie your browser might cache an HTML file but not the content it refers to). Most importantly, though, you can't simply disable HTTP caching when you notice that you…

Post by mercer » Tue, Jun 06, 2017, 1:40 PM UTC

pfooti wrote: post #160

lilbobbytables wrote: post #123

Earlier quoted context omitted.

I'm interested in this as well, as I haven't dove into service workers. But I'm still failing to see why you can't pull the local data from local storage and show it, then render the data from the server (should you get new data)?

That works fine for your xhr data (and is what I do now), but is idiosyncratic to your library (note that detecting online state, responding to online state changes, etc all add complexity to this seemingly simple module, as does managing cache expiry). You can't do anything about your top level index.html file (or the main js and css assets) though. If the user starts offline the second time they use your app, there…

Post by rhinoceraptor » Tue, Jun 06, 2017, 2:36 PM UTC

floatboth wrote: post #159

littlestymaar wrote: post #148

Earlier quoted context omitted.

> Every discussion about anything in Safari on HN, even if not at all related, for the last year or two has included multiple people complaining about the lack of WebRTC. > Now it's here and there is a new complaint /s WebRTC is 6 years old and it's been implemented in Firefox and Chrome for 5 years now ! Since then there's plenty of other DOM API that where introduced and are not supported in webkit, for instance :…

Fetch is supported in 10.1 (only 2 years after Firefox and Chromium!) They also already have Custom Elements v1 support, which is still in progress in Firefox. Timing and SRI they announced in this release (11). Service Workers is THE big gap, at this point it feels like they're actually very afraid of progressive web apps.