Fuck It, I'm Going Back to Firefox
61–70 of 654 posts
Re: Fuck It, I'm Going Back to Firefox
#62I read the article hoping for something insightful, but when I read the paragraph ...a half-dozen tabs that auto-open on launch thanks to the dozens of extensions I've accumulated over the years[...] I had to stop and say "wait, what?" To leverage his analogy that it is like coming home to a new house to find that most of your stuff is already there, it is like not cleaning your house and not taking out the trash for…
Re: Fuck It, I'm Going Back to Firefox
#63Firefox on Mac still has too many visual issues, and the devs often drag their feet on fixing them. Lion (released 2011) added "bounce" scrolling and auto-hiding scrollbars. It took them nearly half a year to fix the lack of auto-hiding scrollbars nightly builds[1], and even longer for it to finally make it to mainline Firefox. Firefox still doesn't have bounce scrolling. To add to that point, the first high-dpi (ret…
> Finally, it's still not multi-process (though it's finally getting there.) [2] In fact, Nightly now is by default.
EDIT: Ok, downvote me all you want but it's a fact, not opinion. I'd give FF another shot once it's in stable but as it is now I'm not going to waste my time playing on a nightly build.
Re: Fuck It, I'm Going Back to Firefox
#64I'll switch back to Firefox when they stop re-arranging the UI. Every year or so it gets changed. It's what drove me to Chrome in the first place.
Re: Fuck It, I'm Going Back to Firefox
#65The biggest issue I have with Chrome is how aggressive it's been about linking Google IDs with the browser. I've lost data twice by bugs related to not having a linked ID. Please Google, understand this; I don't want my browser linked with my Google account.
But that's their entire business model.
Re: Fuck It, I'm Going Back to Firefox
#66Re: Fuck It, I'm Going Back to Firefox
#67Right now, I have one tab open in Chrome (was debugging a web page) and, including "Chrome Helpers", is using 86 threads and 11% of CPU. Firefox on the other hand has 33 tabs active and, including "Firefox Plugin Content", is using 104 threads and 8.5% of CPU.
Re: Fuck It, I'm Going Back to Firefox
#68I find Chrome's web dev tools to be vastly superior to FF and last time I tried it it didn't look good on my Mac and I had the same memory problems as with Chrome. Until FF get's much faster or better devtools than chrome I'm not interested. Not to mention how often does a Chrome extension hit the front page of HN vs a FF one? Don't get me wrong, I don't love Chrome unconditionally (the RAM usage is crazy but so is F…
Re: Fuck It, I'm Going Back to Firefox
#69For me the performance has never been a problem, but the end of NPAPI support may also force me back to FF.
[0] https://github.com/shotgunsoftware/browser-plugin/issues/13
Re: Fuck It, I'm Going Back to Firefox
#70I love firefox, mostly because of the pentadactyl extension(not compatible with firefox 35, sadly) but it has a huge number of problems. Namely, it crashes far too often. It's extremely frustrating, and no number of bug reports I fill out or new releases ever seems to address the problem. I'm thinking of trying to find a better productivity extension, or go back to emacs type shortcuts with chrome or safari. Of cours…
cvim for chrome is really fantastic. I was like you, up until a month ago. I don't miss FF at all. I'm waiting for someone to encorporate vim bindings, umatrix, and webkit into a package... I can't imagine why anyone wouldn't use it.