Fuck It, I'm Going Back to Firefox

This kind of major potentially havoc wreaking change takes time. Google also has a much larger team then Mozilla, so I wouldn't exactly rush these things.

> So still not in stable and Chrome has had it for what? 4 years now?

Chrome is a much newer browser. At the time Chrome was released, it was the only browser with this design, because it's much easier to do when starting from scratch. Chrome benefited greatly simply from observing the design decisions of Firefox, IE, etc. that had had several years to play out by that point.

In ten years (assuming Chrome is still around then), it will also have similarly antiquated design decisions that make sense to us now, but will be frustrating and obsolescent a decade from now. It doesn't mean that Chrome won't be able to keep up at all with these changes eventually; it just means that it's not great to compare a brand-new browser with one that's been around (and used!)[0] for a long time.

Electrolysis (the name for the project) took much longer in Firefox because they had to essentially retrofit an existing browser that hadn't been designed this way from the start.

[0] If Firefox hadn't had significant market share, it could have made this change much more rapidly without fear of breaking things for existing users. But of course, making sure the browser remains stable for its millions of users is a top priority as well, alongside developing these new features.

I also agree-- the developer tools in Chrome are pretty critical for me, in my opinion they overtook firebug. Whenever I try to use the tools in Firefox or Safari I end up getting confused and frustrated. I use Safari if I'm on battery/traveling because it is a ton more efficient, and then only fire up Chrome if I need it.

I love chrome. I have almost no problems with it. That said, I love Firefox and recommend my coworkers use it as often as possible. This is because while I know I am capable in keeping my Chrome running, I know the majority of them are not.

My one major gripe is how poorly it works with Sharepoint. There have been times in the past where I have been working in Sharepoint using Chrome and I can't use a particular function because... well because Chrome? I don't really know why. I just know it works in FF and IE.

You absolutely must link your Google Chrome install to your Google ID on Windows or you will lose data.

Google Chrome now has a "feature" that will automatically reset your homepage, search settings, wipe all extensions and wipe all extension data whenever it detects an unexpected change to any of your settings files or they do not match up to the PC they are locked to.

The goal was to prevent third parties from hijacking your search engine within Chrome. Things like bundleware installers on Windows that switch it.

The actual result is that all your settings are now locked to a specific PC and will be reset anytime anything changes. As the developer of Google Chrome Portable, this means only your bookmarks move with you as you move PCs unless you're logged in. This also means that even if you backup your Chrome install, if your PC dies, you can not restore that Chrome install on another PC. Your bookmarks will be restored, but you will lose your settings, extensions, and passwords since your profile was moved to a new PC.

This stands in stark contrast to Firefox which is completely self-contained. If a third party bundleware installer hijacks your search engine or homepage, you can simply set them back as they should be. All your extensions, extension settings, etc will continue working as expected whether or not you opt to use Firefox Sync.