3 ms·
here's why I don't care; FF simply doesn't work. No, really, it doesn't... _for me_. I'm sure it works for many, _many_ people, I'm just not one of them. I giv
by EpicEng 9y ago
here's why I don't care; FF simply doesn't work. No, really, it doesn't... _for me_.
I'm sure it works for many, _many_ people, I'm just not one of them. I give it another shot every year and it's always something. This year (~5 months ago) it would randomly stutter (freeze every ~5 seconds) and, of course, when a tab crashed, it crashed _everything_.
Now I know they _finally_ have separation via processes between tabs, but WTH? Why did it take so long? Why did my pages begin to stutter? Why could I find no resolution?
Meh, I'll try again next year, but I'm not holding my breath. Safari on Mac, and still Chrome on Windows.
- ksenzee 9y agoThis is a bit like saying you're not going to try OS X because OS 9 was slow and buggy. The code that made your pages stutter is probably not even in the repo anymore.
- EpicEng 9y agoNo, it's a bit like saying I'm not buying a mac again because I've bought one every year for the last 10 years and they were all crap. Seems reasonable to me.
- dingo_bat 9y agoI get your point. I was in the same boat. But whenever you try Firefox next you're going to be pleasantly surprised. The version 57 update has transformed it into something completely new. The frame drops during normal browsing and scrolling are completely gone. That used to be my number one complaint too. Firefox made my $2500 ultrabook feel like a fucking Chromebook.