71–80 of 242 posts
I wish there was a true war, but unfortunately Chrome has too much domination, expect on Apple's ecosystem.
This is pretty similar to the 90s/00s situation with Internet Explorer! It's an apt metaphor; IE6 emerged as dominant at the conclusion of the first browser wars. Chrome is today's IE6.
Until someone creates a new browser with a new render/scripting engine. Which everyone always jumps on saying "it's impossible", the war is over. Chrome has won. Chrome is currently giving life support to Mozilla and when they decide to axe that, well it's game over for Mozilla. The depressing part is the freedom, the new that the internet once provided is over. It's been turned in to a commercial breeding ground and…
The issue is that Firefox HAS created a new rendering engine, but people don't switch. It has nothing to do with technology, people wont even try to switch. Some for fanboyism, some because they would have to adapt, some don't even know what browser is. What I do consider staggering is how many technically capable people are not prepared to make a switch. Google is slowly closing down the lock-down trap they have nur…
And some because they find Firefox unusable. On macOS, Firefox is a subpar browser—it’s awful for automation (no AppleScript support) and accessibility (with Voice Control on, say “show numbers” in both Safari and Firefox). I could go on in all the ways it lacks, especially if I referenced other HN threads where macOS users talk about Firefox. Many of us try to like Firefox, but Mozilla doesn’t make it easy.
The protocol is openly documented afaik, and there might already be efforts to implement an open server. It also has e2ee built-in.
Of course then you might as well go off and use Firefox, Brave or Vivaldi, but it'd be an option nonetheless, if not quite an expensive one.
Until someone creates a new browser with a new render/scripting engine. Which everyone always jumps on saying "it's impossible", the war is over. Chrome has won. Chrome is currently giving life support to Mozilla and when they decide to axe that, well it's game over for Mozilla. The depressing part is the freedom, the new that the internet once provided is over. It's been turned in to a commercial breeding ground and…
Earlier quoted context omitted.
> Google is slowly closing down the lockdown trap they have nurtured for so many years I think that forks of Chromium which have their own sync are easily thwarting this effort. If nothing else, you can always use Edge.
It's so much more pernicious than that. As long as one company controls the One Rendering Engine to Rule Them All, one company de facto controls the Web itself, and everyone else is mostly just along for the ride.
As long as one company controls the One Rendering Engine, all websites are tested against that One Rendering Engine (i.e. not the truth of the spec).
It becomes impossible to create a new rendering engine without actively copying the quirks behaviours.
> The larger problem, though, is that it's not at all clear that Firefox will remain a viable alternative to Chrome. Its market share has been falling for years, and not everybody is pleased with the directions that the Mozilla Foundation has taken. The creators of web sites have responded by not caring about Firefox; having to retry broken web sites in Chrome is a ritual that many Firefox users have had to get used…
Earlier quoted context omitted.
> Google is slowly closing down the lockdown trap they have nurtured for so many years I think that forks of Chromium which have their own sync are easily thwarting this effort. If nothing else, you can always use Edge.
Chrome to Edge is just trading one monopolist vendor lock-in for another.
https://support.microsoft.com/en-us/microsoft-edge/download-...
Key points: > Much of what appears to be Chrome (or Chromium) functionality is, in truth, provided by servers in Google's data centers. These include bookmark synchronization, the safe-browsing feature, search suggestions, spell-checking, and more. > On January 15, the Chromium blog carried this brief notice that, as of March 15, non-Chrome builds of Chromium would lose access to these APIs. > Anticipating this, dist…
Key points: > Much of what appears to be Chrome (or Chromium) functionality is, in truth, provided by servers in Google's data centers. These include bookmark synchronization, the safe-browsing feature, search suggestions, spell-checking, and more. > On January 15, the Chromium blog carried this brief notice that, as of March 15, non-Chrome builds of Chromium would lose access to these APIs. > Anticipating this, dist…
It's snappier than chrome, seems to hog less resources and I find their containers feature a godsend for seperating my work and personal accounts.
So I'd encourage it, I've been with FF for a couple years now and I love it.