4 ms·

Ugh. Look, I used to use Chrome as my primary browser but I switched to Firefox like a year ago. I tried really, really hard to stay with Firefox. But it just d

Ugh. Look, I used to use Chrome as my primary browser but I switched to Firefox like a year ago. I tried really, really hard to stay with Firefox. But it just doesn't work as well as Chrome. I get that it's not entirely Firefox's fault. Sometimes it is (for instance when things crash in Firefox it almost always crashes my entire browser, Chrome never crashes that way). But it's hard to tell a user to go use another browser when everyone is testing and using Chrome. It's IE6 all over again just in different ways. Perhaps I'll try a chronium fork. Sure it's not as good of a move but maybe I'll have better luck with issues. I'll likely try Firefox again to see if things are better (I usually use Firefox for some things at work anyway).

MrOwen 7y ago
A lot of responses I see on any Firefox HN post talk about bugs/issues which have [mostly] been addressed by Mozilla. This includes separate processes per tab which came out just a few versions ago. The problem is that these issues have been resolved more recently vs a year or more ago. It seems many people tried switching to FF long time ago when those outstanding issues were still there so many didn't left up switching because the bugs put a bad taste in their mouth. At this point in 2019, from my perspective, FF and Chrome are functionally the same at this point so there's really no reason to continue using Chrome.
- BinaryIdiot 7y ago
  You seem to have not really read my comment, made some assumptions and created some straw-men. I'm not entirely sure why. As I mentioned before I switched entirely to Firefox about a year ago. I only switched back fairly recently (Firefox shipped separate processes _years_ ago). I also continue to use Firefox daily at work. It still isn't as good, as much as I hate to say it. Some issues have gotten better but not all. They are still not equivalent (especially in web dev tooling) and many sites, like YouTube, still have weird issues in Firefox (full screen mode on my Surface Pro 4 still doesn't work right; it's like it switches to a weird software renderer). Chrome just _always_ works. And I hate to say it, too.

MrOwen 7y ago

A lot of responses I see on any Firefox HN post talk about bugs/issues which have [mostly] been addressed by Mozilla. This includes separate processes per tab which came out just a few versions ago. The problem is that these issues have been resolved more recently vs a year or more ago. It seems many people tried switching to FF long time ago when those outstanding issues were still there so many didn't left up switching because the bugs put a bad taste in their mouth. At this point in 2019, from my perspective, FF and Chrome are functionally the same at this point so there's really no reason to continue using Chrome.

BinaryIdiot 7y ago
You seem to have not really read my comment, made some assumptions and created some straw-men. I'm not entirely sure why. As I mentioned before I switched entirely to Firefox about a year ago. I only switched back fairly recently (Firefox shipped separate processes _years_ ago). I also continue to use Firefox daily at work. It still isn't as good, as much as I hate to say it. Some issues have gotten better but not all. They are still not equivalent (especially in web dev tooling) and many sites, like YouTube, still have weird issues in Firefox (full screen mode on my Surface Pro 4 still doesn't work right; it's like it switches to a weird software renderer). Chrome just _always_ works. And I hate to say it, too.