3 ms·
I would happily use Firefox, however it lacks good developer tools - it's almost impossible to identify JS memory leaks using the FF dev tools. I also find FF
by osrec 4y ago
I would happily use Firefox, however it lacks good developer tools - it's almost impossible to identify JS memory leaks using the FF dev tools.
I also find FF more resource hungry than Chrome (and Chrome is pretty heavy on resources too).
If they start by making the dev tools better than Chrome's, I know I'd switch, or at least start running it in parallel.
- exyi 4y agoThen use Chrome only when you are looking for memory leaks. FF's devtools are not worse than Chrome, I'm used to Firefox and I find Chrome devtools hard to use. For example, the CPU profiler is much better, IMHO
- mastazi 4y agoI also prefer FF dev tools, even while FF was not my daily driver, I was still using its dev tools. I hate Chrome dev tools with that giant console window that takes up half of the space (even when you are not in the console tab) and even if you choose to close it, every now and then it will come back because somehow Chrome forgot your setting.
- wildrhythms 4y agoYes, I hate this. It's also mapped to open on Esc when the devtools are focused, so if you're trying to get out of some context habitually with the Esc key it will open then too. That and the What's New tab drive me insane (you can disable What's New for a given profile, but my job involves running dev tools in incognito and guest profiles where it's always enabled).
- preya2k 4y agoGive them a chance. I was under the same impression until a couple of years ago. Now I think Firefox Developer Tools are far superior. But I can only speak for the Inspector/DOM/CSS related stuff. These are just great!
- osrec 4y agoI'll give them another try. I was just frustrated when I used them last.