> I'm a developer and a Firefox user.

By developer, do you mean web developer?

I tried to use Chrome dev tools, and they were incredibly easy to pick up; however whenever I try to use Firefox dev tools, they feel embarrassingly awkward. Perhaps it's just the familiarity with the tools (and if so, I am very curious to hear whether you prefer Firefox dev tools over Chrome's), but have a nagging feeling that it's just an inferior developer tool.

Both have their pluses and minuses.

It was delightful when auditing the experiences from a potential new client in Firefox Dev Tools the other day, and realizing that I could see, inline to the target DOM element, JS events tied to them while looking through the source. Saved me a good amount of time.

When I'm looking for pure-play performance auditing, Lighthouse integrated into Chrome's Dev Tools are an obvious win.

So yeah, each have their strengths and weaknesses.

Also, finally they made the whole web console into an editable area, like in Chrome dev tools. I used to be so frustrated that you had only one line where to write code.

> It was delightful when auditing the experiences from a potential new client in Firefox Dev Tools the other day, and realizing that I could see, inline to the target DOM element, JS events tied to them while looking through the source. Saved me a good amount of time.

Just tried that, and wow, that's really cool!

I don't prefer one over the other. They both serve my purposes well enough. Generally, I've found that people who don't like Firefox's dev tools just haven't used them much.

The quality of the developer tools is subjective. Chrome dev tools are pretty much unusable to me, the are as you say awkward and weird, but then again I always used the Firefox tools, so I think they wonderful.

The Mozilla Corporation is a 100% subsidiary of the legally non-profit Mozilla Foundation. They can't pay out their profit to their stake holders. So, the only profit motive comes from Mozilla employees wanting to keep their jobs.