Ask HN: Is Google deliberately breaking Firefox?
21–30 of 81 posts
Re: Ask HN: Is Google deliberately breaking Firefox?
#22Re: Ask HN: Is Google deliberately breaking Firefox?
#23And as some other people it's better Firefox on Android than the app. I don't have to deal with adds on Firefox, the official app always have 2 or 4 adds waiting for the next video
Re: Ask HN: Is Google deliberately breaking Firefox?
#24Seeing how many of the users report the problem goes away if they let Firefox report as Chrome I personally am rather sure this is intentionally from Googles side:
Yes, I believe there are some real bugs, but I also think Google do take advantage of "useful" bugs to force us over to Chrome.
So I have decided to put my money where my mouth is and since last month I am a nebula subscriber. I am also considering Patreon.
Please consider doing the same, and please do write competition authorities in your country and do ask about when they will look into Googles rampant abuse of market position.
Re: Ask HN: Is Google deliberately breaking Firefox?
#25Malice, incompetence... Every team has a mountain of bugs screaming for their attention and a director losing their mind over AI. And no one gets promoted for fixing bugs anymore.
> Every team has a mountain of bugs screaming for their attention and a director losing their mind over AI. I don't know whether to laugh or cry.
Re: Ask HN: Is Google deliberately breaking Firefox?
#26who's going to be their monopoly buffer if FF goes away?
Re: Ask HN: Is Google deliberately breaking Firefox?
#27Re: Ask HN: Is Google deliberately breaking Firefox?
#28Re: Ask HN: Is Google deliberately breaking Firefox?
#29I don't have much problems (Firefox on Mac) but seeing how many others complain I guess it is just a matter of time before I get moved to another A/B testing "experiment" testing how much I can endure before I give up and switch to Chrome (it won't happen). Seeing how many of the users report the problem goes away if they let Firefox report as Chrome I personally am rather sure this is intentionally from Googles side…
I feel its far more likely Google devs are just lazy and don't bother to test in Firefox, much like devs at pretty much every company these days. Unfortunate, but (probably) not part of some deliberate evil plan.