> Part of what made chrome succeed is it came out with a pretty robust set of webdev tools right from the get-go.

I think this factor isn't given enough weight in the shift to Firefox.

At that time, the largest pain point in web development was (by a long shot) browser compatibility.

When developers fell in love with Firefox, they started pushing business requirements away from IE and towards the browser that didn't feel like it was their enemy. Alongside with this there was also massive shift to start taking web standards seriously, which is another area where IE dropped the ball spectacularly

It took a few years, but eventually pointy haired managers got sick of our whining and gave in.

It's hard to state just how much of a game changer Firebug was for web development. Before that your only option was "alert()"ing or outputting directly to the page.

Once Chrome came along with their devtools, improvements quickly escalated between the 2 before Google eventually won out.

I can't recall the exact point in time when my use of Firefox fell off, but it was probably due to the account integrations with Chrome.

Chrome has the advantage that they inherited webkits inspector. The chrome team made improvements, yes, but it originated in Safari

> But also, google spent a mountain of money advertising chrome.

Not to mention preferential treatment like the Youtube anti-IE campaign [1]

[1] https://www.theverge.com/2019/5/4/18529381/google-youtube-in...

To be fair to Google, they also kicked ass on implementation at the beginning too.

Chrome was a lot faster and a lot lighter (in the beginning)

Chrome borrowed their webdev tools from Webkit, who borrowed them from KHTML. Chrome launched with dev tools, but they didn't develop their own distinct version of them for many years after launching the browser.