Yea, I also noticed that, save for the pages with tons of images, firefox has actually been better than chrome in that respect for the last few releases. Now with this fix, I'm seriously thinking of jumping back. Then I'll finally have my sweet DownThemAll again. Many kudos to the firefox devs, performance and memory-usage is very important, and it seems they realized that before it was too late. Even with my 16GB I'd really like to run an extra VM for development as opposed to letting my browser gobble it all up.
Last I tried Firefox, pretty recently, it still needed to address some serious issues, when compared to Chrome:
* Unresponsiveness due to one tab thrashing
* Bad use of screen-space (bookmarks always visible, cannot disappear titlebar like in Chrome [there's only a Windows extension for that], menu-bar takes up another bar of space by default)
* Launching firefox has stop-the-world behavior to check/update extensions -- interrupting your flow when you need your browser most
* Some extensions still require restarts
These are the ones I remember off the top of my mind, I'm sure there were more...
I really tried going back to Firefox, but the cumulative pain of all of these made me go back to Chrome.
Or even not trashing. When one tab asks for username/login with a pop-up ("Authentication Required" one) and you have it saved in some email opened in another tab you can't switch to email tab until you kill the login one.
I call it "god window" (god tab in this case) pattern. Very typical for most old and some new Windows desktop apps.
Firefox's UI is the most customizable of any browser that I know of. You can really make it into almost anything you want. My example: http://i.imgur.com/aMgQBgW.png very clean and functional.
I couldn't find any customization that removed window decorations in Linux. I found ones for Windows only.
Also, I got the (subjective) feeling that Firefox was becoming sluggish as I had 6-7 addons. I might be wrong, but that would mean Firefox is sluggish in general.
As I understand it, windows are responsible for drawing their own window decorations on Windows and OS X, but on X they're drawn by the window manager. So it's harder to mess with the title bar because you're starting from nothing and don't even know which of a dozen decoration engines is actually being used. Upside is that decorations are remarkably consistent under X.
Wayland matches the Windows/OS X behavior (probably because it's easier to just accelerate one big rectangular canvas the process draws on), so who knows what will happen as that catches on.
If you can't do it through extensions, you may be able to remove window decorations using the window manager. The configuration is dependent on the specific window manager that you are using, but it should be possible.
Sorry I took a while, but here:
App Button Remove
the RSS reader in the top-right is Digest
The rest is just moving stuff around/removing stuff with the built-in customization reachable by right-clicking blank space at the top. An even more vertical-space saving configuration I use is putting the URL bar up with the tabs - in that case I remove the extra stuff from it like that star with another extension I forget the name of, but it's easy to find.
Extensions require a restart to be installed, perhaps, but that doesn't seem to be a big issue: you only install any given extension once. If you want to install a bunch at the same time, you only need to restart once.
Which extension are you using? I use Mate and found a Gnome extension that was known to be unreliable and indeed did not work...
I agree the restart is a minor issue, as is the menu bar showing by default, as is the bookmarks bar being always/never there (rather than the more sensible Chrome behavior), as is the interruption of my workflow when Firefox decides to check for updates when I start it, as is the relative laggy UI, ... But these issues add up to a worse experience. Worse by enough that despite wanting to avoid Chrome, I came back to it :(
There are also some Firefox-specific extensions I can't live without any more, the main one being KeySnail[2] which gives me Emacs-style keyboard shortcuts.
That's actually Hacker News being terrible. Their font declaration is just "font-family: Verdana;" so if you don't have Verdana installed (which just about never is installed by default on Linux), it defaults back to the one mentioned in the browser settings (which tends to be a serif font).
Hacker News could've made their font declaration have a fallback (like "font-family: Verdana, sans-serif;") and things would look way better by default.
As for me, I solved it by editing userContent.css and adding a font-declaration for Hacker News myself. (or you could use something like the Stylish addon)
All in all, I'd say it's the fault of website creators.
I too wish it had split processes (although I haven't had a freeze in months), but other than that it beats Chrome in every single way. I am not affected by your UI problems, and I install extensions every other week so I'm not bothered.
So, yeah, I guess you didn't really try. Perhaps you're just attached to Chrome.
How do you get rid of Firefox's windows decorations in Linux? All I could find was for Windows, except one gnome-based extension which is known not to work reliably.
Also, checking for updates when I start my browser is the worst possible time UI-wise. I start my browser when the site I want to visit is at my fingertips, and my working memory is fading as I am waiting for my computer. How do you customize this away?
Sure, the bookmarks bar being always-visible or never-visible is a minor defect, but it is still worse than Chrome's show-in-new-tabs behavior. Showing menu bars and window decorations by default shows bad judgement, but indeed that wasn't the reason I couldn't stay with Firefox. It felt slower, had annoying wasteful window decorations, started with annoying extension version checks, and let bad web apps interfere with all my tabs.
Do you have actual responses for my actual points besides "you didn't really try"?
Maybe multi-process is the reason... I've recently started using Chrome more on my sub-notebook because Firefox gets really choppy even though it has lower memory usage. Perhaps the explanation is Chrome can be scheduled to all four of my 1GHz CPU cores, as compared to Firefox which will be on just one?
As far as I know, it has always been. Unlike javascript which usually runs in a single thread, the browser itself is free to use as many background threads as it wants to load resources, render graphics etc. Only javascript is usually run as single thread per tab (unless the webpage uses web workers).
1) Chrome's behavior where you get bookmarks bar in new tabs is far more useful.
2) Even without the bookmarks' bar, I have 4 bars (window decorations, menu bar, tab bar, URL bar), whereas Chrome has 2 (tab bar + window decorations, URL bar).
Screen-space is still wasted compared to Chrome, and you don't get bookmarks in new tabs.
Again, Firefox has no portable way to remove window decorations like Chromes does. There are Windows-only extensions, KDE-only extensions, and unreliable Gnome extensions.
I switched to Firefox from Chrome a couple of months ago, and liked it so far. The UI is fine, and the speed is also fine. But the MacOS+Firefox+Gmail bug (https://bugzilla.mozilla.org/show_bug.cgi?id=341886) drives me nuts. Can't jump to the start or the end of line while editing the message (OK, it is possible with emacs shortcuts instead of standard Mac shortcuts). Can't select text from the current position to start/end of line with keyboard (emacs shortcuts don't help). I haven't appreciated how much I used these shortcuts for email editing before switching to Firefox. And the bug is open since 2006.
[1] http://i.imgur.com/eBiIZHc.png (Also, no close button on tabs and they shrink down to the size of pinned tabs. All other browsers do that shrinking stuff by default. There used to be a property for that, but one developer decided to remove it. Now you need a custom userChrome.css and other voodoo.)
[2] Sounds close, but 50% of that space are actually unused. There is a lot less room for tabs.
I'm not in KDE, I'm in Mate which has no such feature by default.
Thanks for the second tip, if I try Firefox again I'll do that. Is it possible to get auto-updates at browser shutdown or in the background, when it doesn't interrupt my flow? I would probably forget to ever update them if it's completely disabled...
im using windows and the regular firefox (so it doesnt have this fix) and i notice that chromium always scrolls a lot slower than firefox anyway. which annoys me hehe.
Not when most of that 16GB is in use. At the moment, chrome is using up 3.4GB. Yea, I have a lot of tabs open. Yes, I should work on that. Yes, I'd also like being able to open that many tabs and have my browser perhaps release some of that memory and just reclaim it when I open the tab for reading again.
Docker is real nice, although I might go for pure LXC the nex time I build something. But I'm developing on OSX (as many of us, I believe). So _not_ running a VM is not really possible here. I deploy on Linux, and like to have my environment very consistent, hence the VM. Granted, with Docker/LXC I could probably get by with just one VM and a lot of little apps running side-by-side, but that's not how my current setup and projects work, yet.
At any rate, less memory used by browser is more memory for me, to use any way I want.
I already love the firefox behaviour that when it restores your tabs, it doesn't actually load them until you click on them. Awesome startup speed improvement.
I'd also like being able to open that many tabs and have my browser perhaps release some of that memory and just reclaim it when I open the tab for reading again.
Chromebooks do a great job of this -- inactive tabs are often freed when memory is needed elsewhere, and reloaded as necessary. I wonder if that feature is going to come to Chrome outside of ChromeOS.
The joke being that Docker requires LXC and aufs, which means you are stuck running Ubuntu for now. Fedora is soon going to announce Docker support when 0.7 is released.
For now if you want to run docker on your Mac, the best bet is to use Vagrant + virtualbox (or fusion if you have the provider). This means you have to run another VM to run docker which defeats the purpose of the suggestion of running Docker, so you don't have to run another VM instance.
Chrome became very resource hungry and poor at memory management recently. Sometimes I see half blank pages when scrolling which I've never seen before on the desktop.
This has been a myth floating around since the early days of Chrome. I am and have for a long time been a big fan of Chrome, but it has never been light weight. It's just fast so people think of it that way. But you've always been able to check on the memory usage of tabs and see it just eating up your memory.
I agree. Chrome has NEVER been lightweight in terms of memory. Each tab is in its own sandbox environment. It will need to load resources separately for each sandbox and that chews up memory.
Chrome may be inefficient with memory but I could manage this by closing the tab. Firefox would retain the memory even after the tab has been closed for some time.
That seem's to be the desirable outcome, if the trade-off for perceived speed is a larger memory footprint. Users directly feel the speed, but are less likely to be affected by a larger memory footprint.
Just closing the tab isn't enough to release that memory though.
Lets say you have 200 tabs open, check your computers memory usage, close all of the tabs but one and see how much your memory usage drops. Then close that last tab (or fully quit the program on a mac), and see how much memory you get back.
I typically get about 1/4-1/2 of my total RAM back after closing the program entirely.
The half-blank pages you're seeing is a feature that's recently been enabled. This is a case of latency improvement that visually appears to be worse.
When rendering can't keep up with your rate of scrolling, Chrome will display the part that has been rendered so far and display a checkerboard pattern for the not yet rendered part. Previously, Chrome would just flip the display buffers less often if rendering can't keep up.
Yep. In fact, I've noticed performance appearing to get worse and worse in both my Canary browser and regular Chrome. Canary always seems to perform quite a bit worse than regular Chrome. Not sure if that's just due to bugs because of the unstable build, or further changes they're making that is continuously hurting performance.
Interestingly enough, I loaded the page in IE 11 (11.0.9600) and scrolled all the way to the bottom. It initially used around 160 MB, then reached 240 MB by the bottom of the page.
In Firefox Nightly at the initial page load it uses around 250 MB memory and with scrolling it stays around that.
In Chrome (in Canary too) initial it uses around 300 MB but scrolling keeps filling the memory indefinitely (I stopped scrolling above 1.2GB)