Are you sure it's not just a habit? I've been using FF devtools for few years without issues. There are even some things chromium devtools dont have. Only time i use chromium devtools nowdays is for testing/audit (lighthouse).
I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
I've always used Chrome since I started developing, and I liked their Developer Tools. Since I switched to Firefox four months ago I've had a lot of trouble with FF DevTools:
* debugging is too slow (or my computer is weak, but Chrome DevTools run smoothly);
* debugging is very slow;
* the debugger has some unpredictable behavior, like stopping at all calls that lead to some error, when I expected it to stop at the error properly.
Then 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
Yes, i primarily use ff dev tools. And it has greatly improved in the last couple of years. But there are still some shortcomings. For example websocket frame debugging is just barely on nightly. Load time for a web app with thousands of unminified sources with devtools open is terrible. Plus a bunch of small annoyances. It's not so bad i won't use it. But it does make me wish firefox had the same resources for devtools that google does.
I 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.
Devtools on FF are very good. Extremely rarely do I need Chrome, for tools like debugging svg animations. I suspect the overwhelming majority of devtool users don't have to debug svg.
I must admit that I find Chrome's devtools the easiest to use, but that's probably because it's what I'm most used to.
I work at a web dev company and there's a pretty obvious split between people who prefer FF or Chrome devtools. Every time someone says "but you can do this with x devtools but not in y devtools", it's met with a member of the other party saying something to the effect of "yes you can! it's here!". I think it's just a matter of opinion/what you're used to.
I generally also find the devtools to be better but both Chrome and Firefox have years-old bugs involving source maps, breakpoints, etc. so I end up cycling between the two during any given day.
is it possible the devtools experience is one of those things that is largely dependent on where you initially learned it? firefox is my daily driver, and I can't stand chrome devtools anytime I'm forced to use them
I would love to use FF but dev tools in FF feels clunky and slow compared to Chromium. It also seems to have some kind of rendering slowness on my Wayland machine that Chrome doesn't have (i.e. 3fps). Not that dev tools is on par with something as fundamental as tab grouping, but I share the frustration of Moz doing silly shit instead of polishing the basics.
Just testing out FF devtools, I do appreciate how similar they are to Chrome. The biggest differences seem to be geared towards PWAs, such as auditing w/ Lighthouse.
One or two devtool features are better in firefox, but when I gave it a good try a year or so back I had the devtools get stuck / crash / fail to find an element that's onscreen moderately often - enough that I'm not keen to use it for work by default.
reply