[sombremesa]

It depends on what you do on a daily basis. There are definitely things you can't do in Firefox - chrome://inspect, for example, which is how a JS dev can debug their Jest tests (though for these workflows you can just pop Chrome or Chromium open for a moment).

Otherwise, Firefox has the better API for add-ons and a more 'open' approach in general, so there are a lot more things you can't do on Chrome that you can in Firefox than vice versa. I have yet to see a decent tree tabs extension for Chrome, for example. (They exist, but none compare to the one available for Firefox).

[chii]

If you dev using the chrome devtools protocol client (like using intellij, see https://developer.chrome.com/devtools/docs/integrating), you won't be able to do the same on Firefox ATM.

Edit: I'm mistaken - apparently you can : https://docs.firefox-dev.tools/backend/protocol.html ... So no reason to use chrome as a primary browser or development browser.