Firefox’s faster, slicker, slimmer Quantum edition now out
arstechnica.com
arstechnica.com
Old profile?
Is it faster than Chrome? I'm not seeing a meaningful difference between the two, both are very fast.
This jump for 57, keeps me from wanting to abandon Firefox for Chrome as my primary desktop browser however. I don't need Firefox to be faster than Chrome, I just need it to remain very competitive.
I don't see this as a competition for speed. To me it's more of an effort to get the performance issue out of the way so the real benefits can shine.
It certainly can't be called as "slow" or "bloated" anymore by any reasonable stretch, that's for sure. And that can only help it claw back some market share going forward, but speed alone won't work magic. Firefox needs to once again grab the attention of ordinary computer users the way it did when it first arose from the ashes of Netscape. Fortunately people at that time were fed up of IE and were desperate for an alternative. The big question is, are people desperate for a Chrome alternative now?
Enough with the distractions (ffos, iot, buzzword-of-the-day...), FF is getting back to basics and doing great, let's have more of it!
That's going to be hard, given Android and Chrome are both Google products.
Besides, Google is not exactly famous for internal synergies, for years they had two different browsers on Android and they still have multiple chat apps...
Because of that I'm able to keep the old Firefox which works with ALSA for youtube and such and use Quantum for everything else. Gotta love switches like -profile and -no-remote.
Nice work Mozilla!
edit: Figured I'd give it a try. Really easy to set up and after figuring out how to white list /dev/snd in Firefox it works great. Thanks again!
They may not be faster than Chrome but at least it's neck and neck again.
Chinese characters look like a bad flashback from the 90s when viewed on Chrome, I can't believe they never bothered to fix it.
Firefox rendering speed and dev tools penalty were pretty bad and I'll take any improvement I can get.
I want to switch back, but for that rendering speed, quality of the development tools and sandboxing need to be at least on par with Chrome.
On the other hand, the addons took a big hit, most of my addons aren't supported anymore. And it seems that everybody is searching for equivalents, as http://addons.mozilla.org/ seems to throw nginx errors right now.
think of it this way, why would i switch to firefox to get back to where i was to begin with (speed wise)? firefox would have to be substantially different from chrome to make people make the effort to switch. right now it seems that it is just catching up to the competition. i look forward to the continued updates and will continue to look into the possibility of switching in the future. right now, the speed is comparable to chrome, and extensions seem to be at a disadvantage. a few more months to go for me, personally before trying again.
56 was already fast for me, didn't noticed much difference but it's a good thing they woke up and started doing the work instead of all talk and fuzzy feelings about other personal agendas.
I changed to the "light" theme, disabled animations (toolkit.cosmeticAnimations.enabled;false), turned the title bar back on, turned off all of the pocket/highlights junk on the new tab window, and changed the density to "compact".
I like the experience now, except for the square tabs really bug me.
It seems their developers don't use that arrow? Or is it because Chrome doesn't have it? I'm not using Chrome, but it seems the FF developers do, if true.
I don't usually like to customize but it's mandatory now.
Ironically, I read this blog post (https://hacks.mozilla.org/2017/11/entering-the-quantum-era-h...) in Chrome and Firefox, and on Firefox the scrolling was noticeably slow to the point where I found it distracting.
Edit: Turns out scrolling a simple page up and down causes Firefox to use 40% CPU. Is it not using any hardware acceleration?
It is definitely not happening for me on Sierra 10.12.6 on high-spec MBP-tb late 2016, this FF version really flies. CPU is not low, but FF and Chrome have always been hogs in my experience, as long as they are responsive I don't care too much. I guess it also helps that it killed a bunch of extensions...
Twitter timeline measured with "Live video" open on right-hand sidebar, then "Live video" collapsed:
FF 57 - 225, 22 Chrome 61 - 60, 3
* Firefox could import my bookmarks and, equally important, most passwords without a problem.
* Firefox's syncing capabilities seems to sync everything that's important.
* There's a built-in dark theme, people! It isn't applied to empty tabs, though.
* You can customize the toolbar. Not nearly as powerful as Opera's visual editor but better than Chrome's.
* Many plugins haven't been ported to 57.
* It uses a lot of RAM. I only have two tabs open and 5 plugins active yet Firefox uses 500 MB. Doesn't really bother me because I can sacrifice RAM for performance.
* The unified address/search bar is better than Chrome's because it actually consistently searches your bookmarks and not randomly like Chrome. Also, because you can add metadata to your Firefox bookmarks, you can add synonyms and what not to make searching for bookmarks even more powerful.
* I absolutly love that Firefox makes it possible to create custom search engines via the context menu. Also, you can easily add shortcuts to specific bookmarks? Brilliant.
I think Firefox uses a bit more RAM than Chrome when being just opened with fresh session. The point is - that value doesn't increase so massively when opening more tabs as with Chrome. On my machine with 8 GB RAM, Chrome is just unusable, as it eats the whole RAM and everything starts to swap. If you actually use the browser, Firefox clearly wins regarding RAM usage.
Here, right now, with 136 tabs open and 20 extensions, Firefox Nightly uses 2 GB of RAM, with 0.5 GB being used by 1 one of 8 content processes (so probably mostly by long-running Facebook tab, which is massive resource hog). Chrome would eat the whole 8 GB somewhere around 30-50 tabs already.
I still miss Classic Theme Restorer, but the main reason I used it was to bring back the old FF menu button, as I refused to use the weird "bag of squares" menu that seemed to come out of nowhere.
Still feels like it's in the wrong place, and I feel like I should be able to move it, but I'm starting to get used to the new one.
I get that it's an edge case, though. Has anyone else noticed this or looked into it?
With that method, you can successfully login to GitHub and other services using U2F. Unfortunately, not Google, because Google doesn't check if Firefox has U2F support or not. Instead, it makes the assumption based upon the browser agent.
Having most of extensions unusable - not quite.
Till 'UnMHT' or 'Custom Tab Width' and several other extensions are not present for Firefox Quantum, I stick to 'slow' Firefox 56.
I really want to use Firefox more but I spend a lot of time in GSuite.
What is the use case where someone would require hundreds of tabs to be open?
Also, they are way too easy to close accidentally; bookmarks stay, but if you accidentally closed one of your thousand tabs 3 months ago, good luck finding it in history.
[0]https://chrome.google.com/webstore/detail/onetab/chphlpgkkbo...
Once in a while, I realize that I'm not going to read all of these things and I remove most of them. But I'm glad my Firefox scales up to these use cases.
Anxiety at the "I must read this" a bunch of open tabs can create. Frustration at being unable to find the tab I actually wanted to pull up out of the hundreds available to me. Forgetting something I actually wanted to do because it's buried in an avalanche of windows.
It's kinda funny to watch a colleague who follows that mantra try and find the right tab, sometimes cycling through the 4-5 copies of the same website to find the one with the proper state.
Then I see them do the same thing with terminal tabs/windows and cringe because they can never remember where they are or where their windows are connected to. Given that they have prod access and are connected out there while also developing locally, I'm sure nothing will ever go wrong...
Navigating a tree of your actions or your current context is actually way easier than re-navigating a website. This is especially true with things like API docs where you might open a bunch of things and constantly re-reference them. Saving off trees and supporting a kind of quick-tab-find approach both help here too. This also helps when navigating things like source repositories on GitHub.
We don't tell people to retrieve files externally because their filesystem makes it hard to find things. And we don't really chide people for too many editor tabs open either because we have a navigation panel. Why is a browser any different here?
> Why is a browser any different here?
"navigation panel" In which case the tabs are effectively duplicated, and not of much use.
> Navigating a tree of your actions or your current context is actually way easier than re-navigating a website.
It really depends on the size of the tree, and the speed of page loads. For example, I keep a local copy of the Python, Go, and Boto documentation. This makes navigation fast and simple, even in the slowest of browsers. Click on a link, loaded (virtually) instantly. Hit the back button on my mouse, loaded instantly. One tab, fast as I could ever ask for.
Ultimately, OP was asking why, I answered. No chiding intended, and only a little judgement - but disorder is incredibly ineffective.
I should probably disclose that my lines of questioning cover very broad and unrelated areas. So a lot of what I research is along the lines of the direct question itself, then zillions of offshoots as I read to learn how to interpret the results as I’m frequently delving into subjects I am not deeply familiar with.
Mind mapping software is starting to get close to what I really want, but there are some rough edges to work out.
AFAICT, it's still very common for someone with a "slow firefox" issue to be told to nuke their user profile.
Perhaps it’s a solution for problems caused by too many installed add-ons (that may conflict with each other). I’m fairly conservative about what add-ons I install and don’t have more than 10 installed at any one time.
Both browsers communicate with their owners under various circumstances. Both have it relatively well documented (both with some omissions, as the docs lag behind). Both had screw-ups (probably, non-malicious but just accidental - YMMV) and were caught communicating something (IIRC, non-severe) when they shouldn't have been. Both have their own ecosystem/services (starting with Google and Firefox Accounts respectively) that they actively promote.
This is subjective, but I believe in the large picture neither of browsers has some consistent technological advantage in terms of user privacy (fingerprinting, data leaks, options to block unsafe modern stuff etc). One or another wins over specific cases or introduces some measures before another does, but they feel to be generally on par - at least if we consider available extensions (adblocking, etc) and not just the core features.
The only significant difference I see is that one of the browsers markets itself with heavy use of term "privacy", and other doesn't.
Or, in their own words, Google: to organize the world's information and make it universally accessible and useful
Mozilla: ensure the Internet is a global public resource, open and accessible to all
Intentions and goals matter.
As long as Chrome itself really doesn't do anything particularly wrong, of course. But I think Google (probably because of lots of various rumors) went to great lengths to actually describe what they do and what they don't, and I haven't spotted anything particularly alarming in their privacy whitepapers.
Compared to Chromium (the Free Software part of Chrome), Firefox has the advantage that it has no anti-features in the first place, rather than having the Chromium community trying to keep after Google removing each anti-feature as soon as they notice.
That's a key reason to support them.
Any news on that? Will the introduction of WebExtensions might help?