4 ms·
But Mozilla cannot enforce idealism on the developers. They do already a great job with documentation, but they could and should improve on the dev-tools. Chr
by hutzlibu 7y ago
But Mozilla cannot enforce idealism on the developers.
They do already a great job with documentation, but they could and should improve on the dev-tools.
Chrome dev tools are now in a state, that I only use them for developing and debugging. Built in code editor with autocomplete. And I can debug ... and change code while debugging. And it works great (mostly).
Firefox dev tools on the other hand barely work for me to do some debugging and it is no joy. So no wonder more and more developers skip it alltogether, given the low market share of firefox.
- privethedge 7y agoI personally prefer firefox's dev tools to chrome's ones.
- abraCadabstrax 7y agoBoy, I am with you on this one. Full-time FF user too. The whole CSS grid thing is very well done and useful.
- hutzlibu 7y agoWell, I don't really work with CSS much, but js. Are you consider the debugging tools well done as well? And do you know chrome dev tools? With its elaborate performance tools etc?
- abraCadabstrax 7y agoI currently work more with CSS so I find the debugging tools on both good enough for my purposes. I do know the chrome dev tools and find them to be good, just happen to prefer the FF dev editions ease with layout.
- bishalb 7y agoYeah but it's somewhat laggy compared to chrome's.
- hutzlibu 7y agoTo write and debug code?
- privethedge 7y agoI mostly use Console, Network and Inspector tabs and I rarely debug (in general.) Especially Network tab in Firefox's dev tools is much superior to Chrome's one, IMHO.