3 ms·
I used to think this too, but After seeing some colleagues using FireFox dev tools and making the switch (back) to Firefox myself, I realised that there really
by laumars 8y ago
I used to think this too, but After seeing some colleagues using FireFox dev tools and making the switch (back) to Firefox myself, I realised that there really isn’t that much between the two and in fact it’s mire a matter of what you’re used to.
Much like the debates about other developer tools in fact (text editors et al).
- lucianoci 8y agoIt's all the small things. Till recently there weren't even react devtools for Firefox. Almost any dev-oriented extension targets chrome first. Chrome has a great devtools protocol, and node conveniently happens to support it too, which is also why many node debugging tools will use chrome. I use Firefox for casual browsing, but all work-y stuff I do in chrome. Sometimes I'll start debugging a site in Firefox and then some behavior is a bit "off" or missing and I just go back to Chrome. And the only reason I'm using Firefox is because it's not Chrome. I wanted a different browser that looks a bit different to always be aware of the difference between work and personal.
- PJDK 8y agoIt really is the small things. The one that gets me constantly is that you can't resize the columns in the Network tab. I appreciate a lot of the stuff Firefox has been doing, but Google was very wise to realise that first class developer support was the winning move.