Gregory's Server@mitch You know how we spent years building Service Workers and Background Sync and Periodic Background Sync and fixing storage quotas for large-volume offline data?
Um, yeah. About that (latest dev channel, fresh profile):
|
7 comments
 @mitch The tragedy in both instances is that the teams that dropped turds in Chrome have faced no pressure to move to open, interoperable APIs, meaning other browsers (including other Chromium ecosystem browsers) feel forced to include them to make sure that Google's very popular web properties "work right". This also keeps web APIs from advancing because teams that would push them forward already have theirs, Jack. It's not Android levels of bad, but it's bad. @slightlyoff woah. Thanks for sharing. I was aware of the volume size b/c of my runaway cache at work but the rest was news to me.  @slightlyoff @mitch what does this screenshot demonstrate? that docs offline is preinstalled? @slightlyoff @mitch how does it work around web APIs? are you saying it's able to do so because it's preinstalled instead of being a real extension? @hipsterelectron @mitch Yes, it's pre-installed, and it's using Extensions capabilities (superpowers) to do high frequency data sync and other things that should be left to the browser's default heuristics about which sites you use most. |
@mitch On by default, works only on Google properties, and "works around" the limits of the web platform *that we put in place to meaningfully safeguard user battery and storage and bandwidth*. At least it's not buried in `chrome://system` like the CPU monitoring extension is, but no less self-preferencing for it.