[fixermark]

Also not the GP, but at the time: process isolation. The process sandboxing Chrome did that allowed only a subset of it to crash was novel and compensated for their relatively young browser engine gagging and dying from time-to-time. Once I could develop and use plugins without bringing down the entire browser session, I never looked back.

Nowadays: inertia and familiarity. Firefox is sometimes faster and sometimes slower, but there's not enough of a difference to tip my hand, and I already have Chrome configured the way I want (including extensions, multiple sessions, and the keyboard accelerators and widget positions that have burned themselves into my brain). And the cross-platform sync works great; I don't know if Firefox's is better or worse, but it would take more than 0 time to set it up, so I don't care yet.

It's also completely integrated with Chromecast, which I use and enjoy.