3 ms·

Yes. Let webapp developers have their Chrome-only "web" (what's left of it anyway), and us others the web we used to love for ... web stuff. As freelancer/WFHe

Yes. Let webapp developers have their Chrome-only "web" (what's left of it anyway), and us others the web we used to love for ... web stuff. As freelancer/WFHer, I'm already using Chromium for the unavoidable Teams, G-whatever-its-called-now, Zoom, or other videochat/collaboration app anyway and can run these as sandboxed Electron app right now just as well. Or even better since these type of apps tend to require frequent updates of both the browser and loaded JavaScript code due to living on the edge of browser APIs, release-early-and-often, ads, "telemetry", or whatever. While on the way out, please advertise script-heavy sites, preferably with an "application/html" media type for content negotiation and/or proper metadata for search engines, to spare me bulk loading tons of JavaScript when accidentally visiting your page just to leave on the spot anyway. It's appalling browsers had to disable basic HTTP features such as caching because everything can and will be used for fingerprinting. AFAIU, both FF and Safari deliberately chose not to implement the worst offenders in WHATWG's JS API landscape for that reason. Worse, any "cure" for fingerprinting is bound to benefit Google even more as the only ones to receive sensor data of each and every contact individuals make with public information. "It's dead, Tim"

hdjjhhvvhga 5y ago
> As freelancer/WFHer, I'm already using Chromium for the unavoidable Teams, G-whatever-its-called-now, Zoom, or other videochat/collaboration app anyway Tangential to the topic: is there any reason you could not use FireFox? I switched a while ago and was pleasantly surprised to discover all web apps work perfectly, including the Zoom webapp and Google apps (these always feel bloated no matter what browser I use).
- tannhaeuser 5y ago
  I'm using FF all the time (except on iOS); in fact, right now as I type. I guess the reason I'm using Chromium for videochat and customer/work-related collaboration is so that I can close Chromium when I'm done for good ;) and continue browsing on FF for the stuff I care about with many windows and tabs open. Also, I can just nuke credentials for customer-related access when I no longer need those. Maybe I'm burnt by having FF experienced getting slower over time with script-heavy pages (memory or resource leaks?) in the past, and don't want to loose my browsing sessions? It's a moot point anyway since I don't consider collaboration/videochat apps part of the web, so in the end why not have "web" developers target Chrome if they absolutely want to depend on Google. It'll always be more work to target multiple browsers, and developers/bosses will always find arguments to reduce the effort and suck that is browser development/testing. For me, that isn't what the (extant) web is about; there's a reason that a browser, like an MP3 player, used to be more like a decoder/media player rather than all things to all people. I found that, with few exceptions, quality of content I care about correlates inversely with the amount of JavaScript crap on a page/app.

hdjjhhvvhga 5y ago

> As freelancer/WFHer, I'm already using Chromium for the unavoidable Teams, G-whatever-its-called-now, Zoom, or other videochat/collaboration app anyway Tangential to the topic: is there any reason you could not use FireFox? I switched a while ago and was pleasantly surprised to discover all web apps work perfectly, including the Zoom webapp and Google apps (these always feel bloated no matter what browser I use).

tannhaeuser 5y ago
I'm using FF all the time (except on iOS); in fact, right now as I type. I guess the reason I'm using Chromium for videochat and customer/work-related collaboration is so that I can close Chromium when I'm done for good ;) and continue browsing on FF for the stuff I care about with many windows and tabs open. Also, I can just nuke credentials for customer-related access when I no longer need those. Maybe I'm burnt by having FF experienced getting slower over time with script-heavy pages (memory or resource leaks?) in the past, and don't want to loose my browsing sessions? It's a moot point anyway since I don't consider collaboration/videochat apps part of the web, so in the end why not have "web" developers target Chrome if they absolutely want to depend on Google. It'll always be more work to target multiple browsers, and developers/bosses will always find arguments to reduce the effort and suck that is browser development/testing. For me, that isn't what the (extant) web is about; there's a reason that a browser, like an MP3 player, used to be more like a decoder/media player rather than all things to all people. I found that, with few exceptions, quality of content I care about correlates inversely with the amount of JavaScript crap on a page/app.