Multi-process browsing. It is incredibly annoying when my entire browser locks up because one of the fifty tabs I have open is doing something stupid. That never happened in several years of using Chrome, and it happens several times a day in Firefox.
https://wiki.mozilla.org/Electrolysis
You can track the E10s team's progress through their weekly meeting notes:
I have to re-start Firefox every 48 hours or else its resource consumption starts affecting the overall system. This is my primary issue with current Firefox versions, although I am aware that I'm an n-sigma outlier.
Intrestingly, however, the Firefox team has been greatly improving memory management, so that currently, even with my completely pathological browser session, Firefox remains usable for 48 hours with 900 tabs open.
Additionally, the history-tracking of the browser is good enough and my google-fu sufficient so I can find anything I need that I've previously visited.
Keeping my tabs lean makes me much happier!
Then once the browser is restarted it only loads the tabs you actually click on. A kind of tab lazy loading. I wish Chrome had that feature.
The Page Alarm/Tab Snooze extensions are also good for snoozing tabs for say a month until you need them again http://superuser.com/a/533498/7018
I'm sure you've tried them with your browsing habits, but just to make sure.
A crash usually boils down to Javascript taking too long and/or maybe rendering issues with CSS (hardware acceleration). However Chrome is not immune to bad JS and will also slow down your system until the single tab is killed/crashes.
Overall, a crash is not really that dramatic. The browser restarts, all tabs are still there and only load if you click them, you can use Lazarus to auto-save all form inputs and not lose a single point of data and it resumes at the exact position in seconds (no need to scroll either).
Just add NoScript and block the sites where developers can't write decent JS.
>> it happens several times a day in Firefox
If it happens frequently regardless of the sites you're visiting then it must be extensions or hardware acceleration or plugins. i.e a configuration problem and not a FF one
That's true, but with like 8-or-so cores I don't really care or even notice that much (if I notice some tab is eating a lot of CPU power, I just go into the task-manager and kill it, until I need it, at which point I reload it.) No disruption to my browsing experience happens. In firefox, I'll have to close the tab, possibly restart the browser, et cetera.
> The browser restarts, all tabs are still there and only load if you click them
I haven't really used firefox for a while now, but it used to lose tabs occasionally for me. I hope that's fixed nowadays.
Doing one process per tab, which is what Chrome does, comes at a very steep cost in increased memory usage. If you compare a Chrome and Firefox instance holding 20 or 30 tabs, the memory consumption is going to be dramatically different.
Bill McCloskey did a nice writeup on this back in December: http://billmccloskey.wordpress.com/2013/12/05/multiprocess-f...
His article explains how you can try out the experimental multi-process support in Firefox, but that it works differently to Chrome's. I think Chrome's way of doing it wastes a lot of system resources and that we need to be more clever about how we spend a user's system resources.
At least in my experience.
The Stylish extension works fine for me http://userstyles.org/
In chrome, because of the limitations of the extensions API, it doesn't cover chrome pages, developer tools or source view. If you pick a dark background in Stylish and visit a site with a white background, you will see flashes of light because the extension takes over after the document was created and chrome stylesheet was applied.
Check out http://code.google.com/p/chromium/issues/detail?id=1373 for more details
Applescript support. This prevents me from using Firefox.
tell application "Firefox"
activate
set pb to the clipboard
tell application "System Events"
keystroke "l" using command down
keystroke "c" using command down
end tell
set page_url to the clipboard
set the clipboard to pb
end tell
It’s kind of hacked together and I haven’t tested it with rigor but until now it did its job. If you use it, please let me know if you could enhance it or whether it breaks for certain pasteboard contents.It's a bit of a hassle, but for simple things like 'get url of current tab', 'open new tab', 'switch to tab x', etc, it's reasonably simple and can be scripted.
On this ubuntu machine, "the ability to have a bunch of tabs displaying pdfs open at once" is a really big selling point for chrome.
For example, they've disabled custom stylesheets in recent releases despite a clear indication that people were sharing themes, they have very old bugs that don't get resolved (like the stupid white flashes on dark themes), major accessibility issues.
Generally they try to appeal and prioritize regular users (which is fine) but go out of their way to make decisions that ignore power users and not even provide alternatives intentionally.
Finally and the most frustrating part is they don't value feedback. https://code.google.com/p/chromium/ is a joke and a waste of time. The most starred issues are often closed to the public when it reaches a certain level and users are asked to submit a new bug again if the old one is not fixed. This means that if there is still a bug, you have to wait months before other users experience it, find the time to search for the bug and star it, reach enough stars to get attention and then get a response. Bugs are often miscategorized and the wrong team has it in its backlog. It's a mess.
There isn't a feature in Chromium or Google Chrome that Firefox doesn't deliver.
Take it from a serious chrome user and extension developer for several years, switch to Firefox if you want to tweak anything that bothers you easily without having to change the damn source code.