3 ms·
I really want to use Firefox, but their dev tools are lacking in so many ways when compared to Chrome. Fix that, and perhaps even improve on a few things that C
by osrec 6y ago
I really want to use Firefox, but their dev tools are lacking in so many ways when compared to Chrome. Fix that, and perhaps even improve on a few things that Chrome does badly (e.g. JS profiling in the "performance" tab of Chrome dev tools gives you zero information about which functions are responsible for the overhead), and you'll have me converted. I've been wanting to ditch Chrome for ages, but have no suitable alternative for development.
Edit: I've been asked for examples where FF dev tools are lacking, so copying from another comment of mine below:
1) Chrome CPU profiler will display the amount of time taken against calls in line in your source JS files. FF does not do this.
2) Memory snapshots in FF are not sortable, and do not show distance.
3) Performance tab in Chrome allows CPU throttling, FF does not.
4) Performance tab in Chrome also captures much more info, such as node count, heap size, number of listeners, GPU memory.
All the above are very useful if you're building a high performance web app or library.
- uallo 6y ago> their dev tools are lacking in so many ways when compared to Chrome Like what for example? Please be specific.
- osrec 6y agoA few off the top of my head: 1) Chrome CPU profiler will display the amount of time taken against calls in line in your source JS files. FF does not do this. 2) Memory snapshots in FF are not sortable, and do not show distance. 3) Performance tab in Chrome allows CPU throttling, FF does not. 4) Performance tab in Chrome also captures much more info, such as node count, heap size, number of listeners, GPU memory. All the above are very useful if you're building a high performance web app or library.
- tarkin2 6y agoI use Firefox for dev, then occasionally use chrome dev tools for performance. I have to develop for both, so having both open isn’t burdensome.
- Latty 6y agoFirefox's tooling for CSS flexbox/grid has been much stronger than Chrome's for some time. I haven't noticed anything missing from the dev tools since they added proper websocket support a while back.
- olau 6y agoFor a while, I was same, only I was on Firefox and wanted to switch the other way. Then Firebug withered away, and now I find it's awash. But I've actually been running two browsers, one I keep clean for development and one for everything else. If you really want to switch, you could try that.
- miclill 6y agoWhen did you last try Firefox? Chrome may still be better sometimes but Firefox improved a _lot_ recently.
- osrec 6y agoI don't disagree that it has improved a lot, but shortcomings still continue to exist. It surprises me since Firefox is Mozilla's core product - I personally would have expected them to crush Google Chrome in usability and functionality.
- harrygeez 6y agoThis. I use FF for regular web browsing but when I work I still use Chrome for its Dev Tools. It's not even that FF's dev tools are bad -- it's good, but sadly Chrome is still better in some marginal yet significant ways. Most notably Chrome is still better for CSS work when I'm trying out colors, tweaking shadows and animation timings, where Chrome has some nifty widgets to preview changes quickly and easily.