A couple thoughts from the perspective of a web app dev who has struggled with this problem:
I get excited when I hear a proven solution with well-understood scope like “animations and user interactions on the same thread”. I get nervous about ambitious and unknown solutions (async DOM). The web needs a pragmatic fix for animation and interaction and it needs it yesterday. On February 23, 2015 at 10:37:20 , Jonas Sicking (jo...@sicking.cc) wrote: The fact that native is so much better at retaining content to make it available later when the user is offline is one of the big reasons that the web is having a hard time competing with native. ServiceWorkers give us a powerful way to serialize state for offline persistence on a per-app basis. This is also essentially the approach native apps take, right? Your app can persist to a local DB, or not. You can persist via iCloud, or not. It’s up to you to serialize. Magic persistence for complex apps sounds mythical. I want to be wrong about this. --- Gordon Brander Sr Design Strategist Mozilla _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
