The battery usage on MacOS has been atrocious in Firefox 57. Has anyone else had this problem? Am I doing something wrong?
It’s time to give Firefox another chance
21–30 of 733 posts
Re: It’s time to give Firefox another chance
#22Switched to Firefox a while ago. I love it. My little tip is to go into add-ons > Appearance, and change over to a compact theme. It looks a lot better than the default theme imo!
Damn it, I was hoping this was going to alleviate my main worry with this new Firefox - the UI. It's so Microsoft Edge-ified.
I had more trouble finding this setting than I should have. Appears to be hamburger menu -> customize -> (bottom of page) density drop-down -> select compact. Still not sure if I like it. The tabs alone are still way too big for my liking.
Coupled with Ubuntu 17.10 and the Gnome that brings, the top of screen is going to be eaten up by way more UI than I would like. Is there any way to get Gnome to have a unified Ubuntu/application menubar like Unity?
Re: It’s time to give Firefox another chance
#23Firefox has been my daily driver for 2-3 years now. I’d switched to Chrome several years before that but when FF fixed its lag issues I went back right away. Mozilla overplay the “not for profit” card but with Google you can be sure they are collecting and archiving absolutely everything that passes through their servers.
Assuming that one switches to Google as the default search engine (I'd love to know how many do - additionally I beleive Google is the default outside the US anyway), there's effectively no difference. Neither browser does anything special wrt privacy, the same resources and scripts are loaded in both. Safari are the only browser brave enough to try anythng more exciting in this area. (OK, Brave are also in this area, but they're not of much significance right now.)
Sure, Firefox's private browsing does offer tracking protection. But most "normal" users don't seem to use that. And some would argue there's little value in blocking tracking in a session that will be wiped anyway.
Re: It’s time to give Firefox another chance
#24I wanted to try Firefox, but 2 hours into using it I had a meeting in Google Hangouts. Firefox no longer supports Google Hangouts. Back to Chrome it is.
I think it is not up to Firefox to support Google Hangouts but the other way around.
Re: It’s time to give Firefox another chance
#25I use Firefox, Seamonkey and Chromium in rotation to make sure that anything web-related I build works is somewhat cross-browser compatible.
While FF 57 is usable on my Thinkpad 42p I can not say it is twice as fast as the previous version. Maybe the speedup depends on having a multi-core CPU, something which is notably absent in this 2004-vintage machine. Be that as it may, I think FF 57 is about as fast as its predecessor in general: faster in some tasks, slower in others, notably slower in scrolling.
Re: It’s time to give Firefox another chance
#26SeaMonkey (mozilla suite) is the only web browser I have ever truly enjoyed using. I use the browser, email client, irc client, address book, and calendar every single day.
Extremely disappointed that Mozilla has basically given a big middle finger to the SeaMonkey/Thunderbird (comm-central) communities with the removal of XUL/XPCOM add-ons, necessity of multi-process, introduction of webextensions, removal of support for complete themes (show me a single Persona that doesn't look like shit), etc. in FF 57.
The reverberations of this decision are so stark that the SeaMonkey council has announced that it can no longer build off of the nightly mozilla-central tree; they're in the process of building RELEASES from the Firefox ESR branch. It's an absolute mess.
Re: It’s time to give Firefox another chance
#27Am I the only one here who thinks that nothing can beat the Chrome debugger ? Nothing comes even close. It's a different story if you are just browsing, like the 95% or more of the internet consumers.
While it's true the firefox debugger is lacking in certain areas, it's also better than chrome in others. Debugging CSS animations is much easier in firefox, but firefox lacks a way to look at websocket packets. One thing I like about firefox is that its debugger is a just a React webapp : https://github.com/devtools-html/debugger.html . So it's fairly easy to add to it !
I know the chrome dev tools are also just a web app themselves (or at least for the most part are).
I don't know the stack, but I do remember there is a way to open dev tools FOR the dev tools window.
Re: It’s time to give Firefox another chance
#28I was extremely skeptical of all the changes they were doing - I said it myself 100 times, "they're just building a Chrome clone, they're killing all the features I like in favor of speed". But here I am, running Nightly because holy shit this thing flies. Their work has paid off and they're not even done yet. Webrender is coming, it's not quite stable enough for daily use yet (mostly just graphics glitching and inte…
One wonders why all the UI issues weren't solved long ago. Good that they're fixing them now, but what were they waiting for to decide to do it? (Rendering performance is a separate topic, that's been waiting on rust/servo.)
Re: It’s time to give Firefox another chance
#29Earlier quoted context omitted.
While it's true the firefox debugger is lacking in certain areas, it's also better than chrome in others. Debugging CSS animations is much easier in firefox, but firefox lacks a way to look at websocket packets. One thing I like about firefox is that its debugger is a just a React webapp : https://github.com/devtools-html/debugger.html . So it's fairly easy to add to it !
I know the chrome dev tools are also just a web app themselves (or at least for the most part are). I don't know the stack, but I do remember there is a way to open dev tools FOR the dev tools window.
> there is a way to open dev tools FOR the dev tools window
I did not know that.
Re: It’s time to give Firefox another chance
#30Boy, I _really_ didn't want to swap to Chrome. I'd held on through about a year ago, even despite knowing it was slower, a memory hog, and so on; at least this way, _someone_ on my team was viewing our site in FF and would notice discrepancies. I hated to let Google manage yet another aspect of my life.
But as some point, too much was too much. Unable to bear vanilla, Google-owned Chrome, I ended up in (closed-source!) Vivaldi. It was...alright.
About two months ago, I tried out FF Nightly. And by god, it's the best browser I've ever used. And the Nightly builds are (typically) _more_ stable than production-issue from other vendors.
So very happy to be back! Mozilla may have their issues, but I'll gladly take imperfect and pro-user over differently imperfect and profit-driven any day.