3 ms·
You took a link about FF adding a twitter search option and turned it into a rant about how FF sucks and Chrome rules. But ok, I'll bite. I've used the two ext
by onosendai 15y ago
You took a link about FF adding a twitter search option and turned it into a rant about how FF sucks and Chrome rules. But ok, I'll bite.
I've used the two extensively, and the only thing (for my use case) that Chrome has over FF is interface speed. Here are a few things FF does really well over Chrome.
Low level extension access to the browser: This is the reason you don't have Noscript or HTTPS Everywhere in Chrome, it's also the reason mouse gestures are fundamentally broken on Google's browser. For example perform a gesture to open a new tab, then perform a gesture to close it. Oops, you can't, since extensions are disabled in certain types of pages on Chrome due to its security model.
Search as you type: You actually have to hit CTRL+F in Chrome to start finding stuff, versus just starting to type in FF.
Tab activity notifications: On FF, I can have Gmail, Reader, etc.. pinned as app tabs, and if they get updated with new items the tab gets highlighted. Chrome, for some strange reason doesn't do this and you have to keep opening the tabs to check for updates.
Search keywords: Much more straightforward to add in FF, just click on a search field and select "Add keyword for this search". Chrome automatically adds just about every search engine/form you come across to a huge list, which you then have to trawl in order to customize the one you want.
Bookmarks & History: Chrome's bookmark manager sucks big time, I guess Google wants you to search and not bookmark. FF has a half decent manager with tag support. The Wonderbar also works a lot better than the Omnibar when searching your history and bookmarks.
Tiddlywiki: This is the big one for me (although only tangentially Chrome's fault), I use tiddlywiki extensively and FF is the only working browser on non-Windows platforms.
So all of these annoyances in Chrome negate the gain I get from its speed by a large margin. Again, this is my particular use case, but I definitely get stuff done quicker in FF than in Chrome.
And by the way, the initial extension breakage is fixed on FF 7.0.1, which was just released.
- Pewpewarrows 15y agoI also don't think this thread is the place to discuss these things, but since it's here already... Wouldn't search as you type be fundamentally broken on any website featuring keyboard shortcuts? (I'm not a Firefox user, so I don't know how that's handled). Pinned tabs are highlighted in Chrome when they receive updates. The pulsing used to be very eye-catching, but for some reason they now reduced it to an almost unnoticeable searchlight-like effect from left to right over the tab chrome and favicon. In Chrome you right click any search field and choose "Add as Search Engine", just like Firefox. It also picks up on any search that you've done automatically, so you can just tab-search from the URL bar as you're typing a site name that you haven't explicitly added a shortcut for. At the end of the day, they're both very excellent browsers that have almost reached full feature parity with one another. I don't think either one is better, it's just a personal flavor and preference at this point that you can't qualify, equivalent to preferring Chocolate over Vanilla ice cream. In fact, users now have 5 competing, well-built and standards based browsers to choose from. The true winner of this browser "war" was the end-user, which is who should have won.
- sp332 15y agoSearch as you type: You actually have to hit CTRL+F in Chrome to start finding stuff, versus just starting to type in FF. Chrome works about the same as FF for me, I don't see any difference. The only difference is FF's "quicksearch" can be brought up by pressing '/' which is quicker than "ctrl-f".