3 ms·
Not saying I agree with the lay-offs here, but it's incredibly rare I find myself wishing I was using Chrome's developer tools whilst doing web development. I
by lol768 6y ago
Not saying I agree with the lay-offs here, but it's incredibly rare I find myself wishing I was using Chrome's developer tools whilst doing web development.
I have missed functionality when I've had to use Chrome though - like Edit & Re-send for network requests, copy as cURL (which arrived a few years later to Chrome), the accessibility inspector (which is not Lighthouse), services like https://profiler.firefox.com/ https://profiler.firefox.com/ etc
I think the only thing I have found that Chrome sometimes performs better on is source maps and breakpoints in prettified code.
- dmix 6y agoI’ve always believed that Firefox dev tools probably had most of the things I need but the interface is always...uglier and less familiar, so I don’t bother. It’s a low threshold to just use Chrome for development and FF for everything else. Also I believe the OP was talking about more development tooling than just the front-end browser dev tools. Chromium always seems to have the most advanced debugging tools for browser development at the systems level. At least from what I’ve read...
- feanaro 6y ago> I’ve always believed that Firefox dev tools probably had most of the things I need but the interface is always...uglier and less familiar, so I don’t bother. Is it just familiarity? Because I feel the same way about Chrome.
- ehaughee 6y agoI consistently have to switch to Chrome devtools as FF (my default browser) devtools crash or hang on large (1.29MB gzipped) bundles like one of the apps I regularly maintain. While we want to do some code splitting, module lazy loading, and refactor to make tree shaking more effective, the fact that Chrome just works when FF does not is very frustrating.