[j-conn]

Personal use aside, I've been meaning to try out firefox for development after seeing some of their release announcements here. Any tips for people like me who are accustomed to chrome devtools? Are there some things you can do in firefox that you can't in chrome, and vice versa?

I do look forward to the chrome devtools release videos, always learn something new.

[robin_reala]

Firefox in general has much better CSS debugging, and somewhat less good JS debugging. If you’re going to try it out then I’d suggest looking into its grid / flexbox visualisation.

[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.

[fraudsyndrome]

I work with both and generally they overlap quite a lot for the basic stuff - for general ones, you probably just have to get used to the colours.

I use firefox for dev and browsing but my job requires me to check out chrome more because it's used the most. One thing I find myself using firefox for is the feature of visualising a flexbox which chrome doesn't have.

[dexterdog]

I use Firefox for meet calls every day