[rkagerer]

I tried for the last several weeks to switch to Firefox ("normal" edition) after Google introduced new mechanics pushing account login, but ultimately, and disappointingly, found myself drifting back to Chrome.

Main reasons were speed (Firefox opened slightly slower, and there seemed to feel like subtly more per-character latency typing in URL's) and minor anti-native behavior (the default-disabled-until-you-move-your-mouse Save button was particularly annoying, even though I understand the rationale).

I got the dreaded "Firefox process is already running" dialog a few times and had to close all my windows (ugh). I really missed Session Buddy; tried alternatives like Tree Style Tab but they weren't as clean.

Finally, one or two pages didn't render / operate properly (guessing due to non-cross-compatible JavaScript statement buried somewhere in them).

Unfortunately I don't have the time to create good step-by-step reproducibles and log bugs. I know some of this can be tweaked out via preference settings. I even spent some time tailoring my userChrome.css per suggestions here. But just couldn't get everything to work quite perfect. FF will have to spend some more time as my secondary browser, may give it a shot again in another year or so or next time Google pedals something stupid. Will try out the new devtools when I'm working on a page, maybe that'll be the hook for another attempt.