It is true the Firefox's dev tools are a lot better now than they used to be - I use them regularly when I test sites cross browser. But they lack critical features like source editing and stack rewinding, and the tiny visual/layout improvements they've made are not enough to get over that. In Chromium, if I pause a script, I can edit a line code earlier in the function, resume, and Chromium will rewind the stack to that point and replay it forward with my changes.
It is insanely useful, hands down the single tool that I use most often. Stuff like that blows Firefox's dev tools out of the water, because it turns out that I debug Javascript more often than I debug Grid layouts.
A while back I looked into whether or not anyone at Mozilla was working on something comparable, and there was somebody. But then everything went silent and I don't know the status anymore. I've been wondering for multiple years now why this kind of stuff isn't higher priority than new Grid tools or color selectors or whatever.
Firefox's dev tools are way behind Chrome's in basic functionality, even if the user experience is otherwise excellent. You can't even set breakpoints on DOM elements. I would disagree with anyone who claims that they're even remotely comparable tools at this point.
Based on what? What did you try to do and couldn't? Or is your complaint - like the rest of your comment says - that you weren't immediately familiar with the UI, you didn't bother learning, and then decided it was the browser's fault?
How long did it take originally for you to learn the Chrome tools and how long have you given Firefox?
It's a pretty widely held thing that FF's dev tools don't feel as smooth or well thought out as Chrome's, which is frustrating because FF (really, FireBug, unless you count the weird IE stuff) pretty much _made_ the concept of browser tools great.
I'd love to use FF again too, but for me the blocker is the UI and battery drain. 's why I just use Safari.
I agree, but how is this relevant to my comment? I didn't say the GP did anything wrong - I asked them what they did. Not nearly the same thing.
> It's a pretty widely held thing that FF's dev tools don't feel as smooth or well thought out as Chrome's
There are a large number of groups with widely held beliefs where said beliefs don't stand up to scrutiny. "It doesn't feel like Chrome" is not a belief that doubles as valid criticism because it's not actionable. Its sole purpose is to complain about things while making sure nobody can ever act on them because it's so vague.
> for me the blocker is the UI and battery drain
While "the UI" fits in to the category above, battery drain is an actual, specific, measurable and actionable complaint. So please, more of the latter, less of the former.
These are not things that Firefox just does differently, they're features that Firefox just doesn't have.
Firefox's dev tools aren't bad in and of themselves. The UX is fine, and getting better. I don't know if other people have opinions about memory tools or profiling -- I don't all that much.
I guess Firefox's dev tools look prettier, and they do have some features that Chrome doesn't. But Firefox features tend to trend more towards, "here's a cool thing like the ability to debug shaders". Chrome's trend more towards, "here's a useful thing like the ability to debug Javascript."
Firefox container tabs are game changing.
(Before I get you-can-do-this-and-that replies, I know Profile Manager exists, and that's an ugly hack: macOS users should not need to run multiple copies of the same app bundle.)
The big thing that's different with container tabs is that after you set it up (which is done little by little as you decide to open something in a specific tab and then mark it to always open there), it's not something you actively manage, it passively does what you want. That's why it's so different.
Having every site be it's own container (which is also a mode Firefox supports, to my knowledge) would be slightly more passive, but also likely cause problems with some sites that use multiple domains, so I think container tabs is a good compromise (for now) that allows good compartmentalization while also allowing escape hatches for sires that require it.
If you ultimately do want to keep using chrome for the dev tools, you can switch your primary browser to ff and use Chromium (without signing in at all) just for that purpose. There's no reason you have to use your primary browser for your web development work.