Ask HN: Is Chrome now the standard for web developers?
I've been using Firefox in combination with Firebug for years and it seemed that most web developers are quite fond of that combination. But in the recent year or so the development of Firebug not only has slowed down, but seems to be target of mockery.
I've been listening to a ton of podcasts this year and everytime the topics browser or development tools comes up people are talking about Chrome. Sometimes mentioning Firefox with a certain tone that implies "If you're still using that old...".
I'm surprised. I like Firefox as my main browser. But there is probably a connection between the development speed of Firebug and the popularity of Chrome's developer tools. Having two browsers running using only one of them to develop feels rather odd, but I feel like I'm missing out otherwise.
What happened that made Firefox vanish out of the vocabulary of most developers?
13 comments
[ 3.5 ms ] story [ 47.3 ms ] threadAlso, Firefox is a great browser!
https://developers.google.com/chrome-developer-tools/
I'd be interested in what you get out of Firebug that I don't get out of Chrome's debugger.
What sold me was better memory management and better (in general) CSS3 rendering. I normally work with two windows open, one that has all my cookies and stuff so I can do web searches, and another with a blank persona so I can do development. Having two instances of Chrome running vs. one instance of Chrome and Firefox running seemed to lead to less crashes.
Regarding the dev. speed of Firebug, the lead dev on Firebug went to lead up work on Chrome's Dev tools[0]
I still find Chrome's dev tools lacking and the interface hard to navigate. I also miss the plugin ecosystem that Firebug had (I could send xdebug messages straight into Firebug, which was amazing!)
[0]http://news.cnet.com/8301-30685_3-20080338-264/firefox-world...
It took FF less than a year to get their st together and fix their browser. Today it's great, but the harm was done. Most of the people who moved to Chrome never looked back, and still remember FF as a slow, annoying browser.
I'd also like to say that Chrome is in no way a standard and shouldn't be considered as one by any developer worth his salt. If you make a website that doesn't work as well in firefox, you have lost my respect. (unless you are doing a Chrome experiment or something).
Use the tools we have. Use all of them. Make sure your code works everywhere (reasonable - I.E. 6 is as far back as I go currently) Anything else is a disservice to your self, your craft, and your users.
Editorial: I'm not sure this is a good thing. Chrome DevTools can be used to influence the web dev ecosystem and Google has very different interests than most developers. But so far they seem to be playing fair as best I can tell.
That being said, I am really not a fan of the in-built Firefox dev tools. For the life of me I don't understand why Mozilla are dedicating their time to building up their own dev tools when Firebug is the preferred environment for front-end devs that use Firefox. Again, this could just be down to personal taste, but it feels like it's a wasted effort. I'd prefer to see those developers spending time on improving Firebug.