Hacker News new | ask | show | jobs
by slimypi 1390 days ago
Jeeezuuuss! that will hurt, a lot.
4 comments

Firefox is not that bad. Honestly the multi-account containers alone merits the switch.
I don't get where "not that bad" is coming from with Firefox these days. Firefox is just plain good, and has been for a while.
I don't trust Mozilla. They continually make changes against the interests of the computer literate, they continually screw with the UI, they continually take control away from the user, they are literally in Google's pocket, and their own attempts at fundraising put the lie to their claims about privacy.
I don't understand this reasoning. On one hand everyone complained that Firefox was to slow to bloated could be brought down by extensions etc. and moved to chrome because it was faster. Then Firefox implemented changes to make it faster, isolate extensions etc. and everyone complains that they killed them off and doesn't think of the users. Now we have the situation that people say they can trust Mozilla, because of these changes, while at the same time they stay on chrome.

I have two issues with this, 1. Chrome is so much worse in respecting its users, it is completely hypocritical to say not to trust Firefox but use chrome. 2. All these posts are actually painting the impression that there is no valid alternative, in fact that chrome is the less bad (freer) choice compared to chrome. This creates exactly the narrative that Google wants, that their choices are really just minor inconveniences and there is no valid alternative to chrome. I mean just in this thread we have seen many posts that state that Mozilla is essentially doing the same just slower and cant be trusted, despite statements and actions to the contrary.

Chrome is not to be trusted; this I agree with. Chromium forks on the other hand, like brave or vivaldi, have none of these problems. The former has already committed to not implementing this garbage restriction on blockers. Chromium's engine is solid from a technical standpoint and doesn't have any inherent privacy issues aside from being owned by Google engineers.

If it sounds like I'm holding Firefox to a higher standard, I am. Their own positioning in their own marketing is based on a moral stance on privacy and "empowering the user". They have demonstrated that this stance is held out of marketing convenience rather than sincerity.

Chrome is the devil you know, you know it is made by an ad company, is filled with tracking, and will always act to support that. Firefox is… Not who they make themselves out to be. That's almost worse in a way.

You think a crypto company and a closed-source browser have your best interests at heart?

You do you.

I think Firefox is an important alternative to WebKit/Blink-based browsers.

But as a web developer I semi-regularly butt up against bugs in it that have languished in Bugzilla since like, 2014, with absolutely no progress on them.

I have dealt with two (maybe three?) bugs in Chrome ever and one of them was a pretty clear fuckup they rolled back within days.

I've dealt with many nasty rendering bugs in chromium that were never addressed, from weirdness that just made rendering a bit ugly, to spec-incompliant layout (that also differed from other engines), to iframe-related stuff that left half of the frame completely white, to animation/transition related gotchas, to outright renderer crashes, including some that brought down the chromium wrapper process (which may have been security risks, but figuring that out isn't easy). And ditto for firefox. This is years ago by now, but my impression isn't that chromium doesn't have bugs nor that it fixes bugs promptly, but rather that all websites and web-toolkits necessarily are designed with chromium limitations in mind. That's certainly what I did - no point in releasing anything that doesn't work on chromium; that'll just get you laughed at and ignored.

The chromium bugtracker too is full of ancient unresolved bugs, just like gecko's bugzilla: https://bugs.chromium.org/p/chromium/issues/list?sort=id, and I'm sure that if you wanted to you could find a ton of decade old bugs that leave you wondering how those weren't fixed by now.

This just seems to be a fact of life with various browser engines. There are surely all kinds of more or less reasonable motivations to ignore those old bugs, but whatever the cause it's certainly the status quo.

I've only got a very tiny and rudimentary homepage, but when I finally got around to adding some basic stylesheet to it, I almost immediately managed to run into an issue with Chrome(ium)/Blink.

I also managed to find another case where of all things Internet Explorer (!) was the only one (possibly EdgeHTML, too, but I don't remember that any more and now it's been replaced by Blink-based Edge, I can't easily check it, either) that got things right.

From my experience, almost every website doesn't feel as nice in Firefox as it does in Chrome. Ofcourse some of those sites are maintained by Google (YouTube).
And some things don't even work. For instance, my dentist had a sign "rate us here on google" with a QR code. That code didn't work on my phone. I eventually figured out that it works fine in Chrome, but doesn't work in Firefox. In fact, there's no way to rate businesses on Google.com from Firefox on my phone. The links just aren't there, and going directly gives a 404.

Everything works fine on Chrome.

That's obviously done maliciously by Google, of course.

Chrome/chromium based, is worse than IE in this regard - because of Google specifically, we've moved from "viewed best in" to "only works in".
It's excellent! I've been using it for three years now with zero problem.
I agree, this is a really useful feature.
I use firefox so i don't know much about chrome vs chromium politics, but if the chromium people have one thing to do now, it would be to maintain manifest v2 in their fork..
Unless something recently changed, Chromium is considered upstream for Google Chrome, not a fork... so you will see most engine level changes originate in Chromium, by google engineers.

Maybe you are confusing it with de-googled-chromium et al?

Ah right, now i remember. Yes that would be de-googled-chromium then.
chromium people are chrome people. google provide chromium either as a literal requirement for compliance with some other open source licence, or as a vestige from the “don’t be evil” days.
Meh, just use Firefox for general browsing and Chrome/ium for the one or two things that only work on that.
It's shocking that in 2022 there are still sites that (or have been forced) to only work in Chrome.

Looking at you Google search results [1] (but I understand their motivation), however I do have one local company site that refuses to move beyond their loading splash in Firefox.

I guess I should be thankful it's no where near as bad as the IE6 days where HTML standards were completely disrespected in the quest for more market share.

[1]: https://addons.mozilla.org/en-US/android/addon/google-search...

User agent spoofing seems like what should be done on the user's end in those cases, if it's not possible to avoid using such sites for whatever reason.

Problems would begin once we'll eventually get Chrome-specific functionality or something that Mozilla won't implement due to a variety of concerns, thus simply breaking sites: https://mozilla.github.io/standards-positions/

Then we'll basically be back in the days of IE, except that this time Google will be the ones with the browser monopoly, if we're not already there somewhat - the majority of folks haven't even heard of Firefox.

Didn't Google say it was going to make Chrome have the same generic user agent forever in the future? Seems like using that one will be the way to go once that happens.
My experience is it’s more often proprietary web fronts for corporate microservices than WWW pages

If Firefox won’t work, edge almost always will. I’m really trying not to download chrome again. I forgot chromium is an option. Is that not maintained by Google?

> Chrome/ium for the one or two things that only work on that

Firefox has been my daily driver for close to a decade, and I've not run into something that didn't work on it, but worked on Chrome.

It's mostly some specialized features, like conferencing in Microsoft Teams. Clearly some pieces of web software are optimized only against webkit/chrome. But yeah, not many things outright refuse to work on Firefox these days.
Embrace, extend, extinguish.