3 ms·
In that case, you'd likely prefer a JS based app that used its app manifest to cache the actual moving parts (JS/images) before you headed on vacation and lande
by twistedpair 13y ago
In that case, you'd likely prefer a JS based app that used its app manifest to cache the actual moving parts (JS/images) before you headed on vacation and landed on that slow connection. Now it only makes a bare minimum of compressed RPC's to provide the page with the content to render itself. Depending on the content being rendered, you could even get an RPC down to one or two packets, much better than sending you the entire site frame over and over for a minor change (I'm looking at you classic postback driven ASP app).
- masklinn 13y ago> In that case, you'd likely prefer a JS based app that used its app manifest Speaking as somebody who's been in that case, no. 1. The app manifest doesn't need "JS-based apps", they're indepedendents 2. Assets caching doesn't need the app manifest either 3. Stop breaking stuff which works. HTML works, your shitty application does not.