[more-coffee]

It is pretty fundamental. While Safari lacks features, it feels so much lighter and is noticeably less memory/CPU intensive. As a developer who needs every MB of memory, this makes me resort to Safari for pretty much everything. I'll occasionally use Firefox/Chrome when I really really need their superior webdev tools.

[Raidion]

What tools in FF do you think are better than Chrome? Honestly, my computer is beefy (and firmly attached to a power source) enough that performance is rarely an issue with any browser, and Chrome dev tools seem to be superior in most ways, with the slight exception that it's harder to see what events are bound to an element, but the software I develop usually has fairly tight couplings so that feature isn't needed often.

I need someone to make a case that FF dev tools are better than Chrome, simply because without performance being an issue, I need confidence that switching would be a net productivity increase despite having to learn the slightly different tooling of the FF dev tools.

[more-coffee]

Well don't listen to me, my work is mainly backend. The only frontend work I do is restricted to side projects. But most frontend devs I know prefer Chrome. My personal preference to FireFox is paranoid me trying to avoid Google (but that's another topic).