[Libermentix]

In my opinion, that is exactly what made Chrome popular. Focussing on Dev-Tools, but that's a very expensive undertaking (it took firefox an extension to make this possible -> Firebug ftw). However, market success from other companies e.g. Stripe have shown that optimizing for developers today is by far the most effective way to get into market.

MS did the same thing, although back then they used ActiveX extensions or certain proprietary IE implementations that simplified the transition from old fat-client development to web-development.

Now that this is gone, focussing on debugging and open-sourcing is a better choice for a web-browser to win dominance. Chrome did just that: Opensourcing the core - attacking one of Mozilla's core promises - and adding proprietary google eco-sytem add-ons on top of that.

So imho what made you change to Chrome is similar to what made everyone of us developers back then adopt IE (i.e. simplifying development). And when Chrome started gaining traction, the google-lead team started implementing proprietary APIs that we now struggle with when we consider an open non-proprietary web.

I use firefox everyday, for dev and regular, and I'm happy to be a user. But I also see a lot of sites that just start breaking because they have been implemented with Chrome in mind. For where I am standing, I try to encourage our team to develop for FF first, test in Chrome and then EDGE/IE, that way it's most likely that anyone can access the site without breakage. And yes, this also means that sometimes it takes some overhead, but I'm willing to take that for the sake of an open web ;-)

[dogma1138]

Firebug is better than chrome dev tools mostly.

The problem is stability especially for development, a rogue JS script can still kill a browser, chrome loses a page, Firefox loses its mind.

[Libermentix]

Indeed, I love Firebug and have been an avid user since it first came out.

For the rogue JS, that is indeed a problem. From a development perspective though, I even think this is a good thing: stuff that bricks your browser needs to be optimized first. the moment we'd allow a more easy grip in terms of development, a lot of slow stuff will find its way into the codebase.