At the time chrome was slightly faster and more efficient… Chrome actually forced Firefox to modernize its browser to stay competitive.
Comment on Google Chrome pushes ahead with targeted ads based on your browser history
MataVatnik@lemmy.world 1 year agoHow people threw Firefox aside for Google Chrome, at a time when good was known for shitty practices, will boggle my fucking mind.
jimbolauski@lemmy.world 1 year ago
MataVatnik@lemmy.world 1 year ago
People keep telling me that, but everytime I tried Chrome my computer would lag and the fan felt like it was getting ready to take off. On multiple conputers
Magnergy@lemmy.world 1 year ago
When it first took big bites out of Firefox, it wasn’t slight at all. I have only my hazy human memory on this, but some pals and I ran a test script at the time. Iirc, Chome would routinely load enough to start reading in 2 seconds while Firefox was more like 6 on average with our site list and went over 10 way too often to ignore.
It had been very easy before that to blame the sites for all the crud they were larding in. But it was like Google’s clean, fast search page compared to Yahoo’s “junk you don’t need” frontpage all over again. Chrome won on speed fair and square.
Thus ends this yarn by one internet fogey.
vapeloki@lemmy.world 1 year ago
Another answer: Netflix
While the Mozilla foundation had designed browser DRM that worked on Linux, Chrome has the first implementation. And that enabled Linux users to watch Netflix.
Next one: forced fucking cloudflare DNS over HTTPS. I dipped Firefox because of that.
As shitty as google behaved, that was a nono
MataVatnik@lemmy.world 1 year ago
Could you give me an eli5 on the DNS part?
vapeloki@lemmy.world 1 year ago
Sure, Firefox introduced a security feature: DNS over HTTPs. So instead if asking some DNS server that is configured on the local system, for the IP that belongs to a Domain name, am external service is asked via HTTPs.
While this is in theory a good idea, and has some benefits, the Firefox implementation was bad:
Users, that where forced into DNS over HTTPS could no longer resolve internal hostnames. This was a killer in office environments. And after the fix for that, everything was first submitted to cloudflare and only if cloudflare could not resolve the hostname, the local DNS server was asked, leading to potential information leaks. Also a no go for companies.
Firefox has fixed these issues by providing privacy policies, the option to choose other DNS over HTTPS providers and the option to define what domains should never be resolved externally.
But they lost trust in many professional environments because of that move.
MataVatnik@lemmy.world 1 year ago
Thank you. Yeah that sounds like a really bad move on their part.