Is there any work on having something like HTML5 lite with a lighter browser implementation?Because things like these call for more devices(sockets) to used , which takes more resourceful computers to accomplish.Is there any work on actually reducing the browser foot-print , right from spec level?
This is exciting. I don't track too many of these standards efforts closely, but I've been following this one for a while. I honestly think that offline-first will do more to close the gap with native than anything.
> It's like having a proxy server running on the client
Is that "proxy server" under the control of the client or the origin site? e.g. can it perform content transformation? That post talks mostly about offline caching, are there other use cases driving the proposal?