6 ms·
This is not defending it, but the annoying situation is that I am finding myself sometimes forced to use Chrome. I don't use it as my primary browser and it I
by nerdjon 3y ago
This is not defending it, but the annoying situation is that I am finding myself sometimes forced to use Chrome.
I don't use it as my primary browser and it I use it at an absolute minimum, but more and more I see popups of being unsupported in Firefox or needing a critical plugin for a workflow at work.
I do worry that we are seeing a repeat of that situation, a bit different but the same idea. A browser having too much control and shaping things their way.
- starttoaster 3y ago> This is not defending it, but the annoying situation is that I am finding myself sometimes forced to use Chrome. ... but more and more I see popups of being unsupported in Firefox The obvious suggestion here is to use a Chromium-based browser that is not Google Chrome. Like Brave.
- bagacrap 3y agoIs there a reason to use brave besides being a contrarian? Why do you trust brave? They've had their own share of controversies. And it's still a chromium browser. Sure they could disable evil feature X, if you trust them to decide which features are evil and Chrome doesn't have a setting to disable that feature, but if Google decided to remove a feature that you liked, Brave would have no way* of adding it back. * Afaik they aren't really staffed up to maintain a fork so much as tweak settings and repackage
- deleted 3y ago[deleted]
- starttoaster 3y ago> Why do you trust brave? They've had their own share of controversies. Not incredibly relevant, I suggested to use a different browser. If you don't like my suggestion, input your own valid replacement to Google's Chrome. Talk about being a contrarian. You also seem to mistakenly believe that Brave is a child of Google Chrome. Brave is a child to Chromium, and Google Chrome is a child to Chromium. This article states that the Topics API is being added to Google Chrome. I made my suggestion on the assumption that they would have said that Google added the Topics API to Chromium if they added it to Chromium. If the article worded this poorly and they actually meant to say that Google has sunk this in to upstream Chromium, then I cheekily alter my suggestion to W3m or Lynx.
- bagacrap 3y agoGoogle Chrome and vanilla Chromium have little to distinguish them outside of branding. The difference is not one of repositories but of build flags. Suggesting Lynx as an alternative clarifies that your remarks are unserious, or you are out of touch with reality --- charitably I will assume the former.
- meepmorp 3y agoSame rendering and JS engine. That's just monoculture where you slapped some branding on things to make it seem more varied.
- starttoaster 3y agoBut is the Topics API part of upstream Chromium? Because I'm not a browser developer, but the article does not say that the Topics API is being added to Chromium. It says that the Topics API is being added to Google Chrome. I don't want to presume the outcome of whatever you respond to the former question with, because as I said, I am not a browser developer. But it would seem to me that your argument is irrelevant to the conversation at hand.
- prox 3y agoMe too. What I sometimes do when I get a sense of “works only in Chrome” is write a complaint to the company. At least make it known.
- 2OEH8eoCRo0 3y agoUnless it's required for work- don't use sites that don't work in Firefox.
- helij 3y agoI rarely experience something not working on Firefox. When I do I go with Brave which usually works. If it doesn't I fire up an email or click on Contact Us page and send an email. Most of the time companies are quite responsive and fix this.