3 ms·

Very cool, but I'd much prefer they spend their time bringing Firefox's dev tools up to par with Chrome's first. I've tried several times to switch to FF comple

by _bxg1 7y ago

Very cool, but I'd much prefer they spend their time bringing Firefox's dev tools up to par with Chrome's first. I've tried several times to switch to FF completely, but every time I end up switching back on my work computer because of the dev tools.

udfalkso 7y ago
I recently switched back to FF after many years on chrome and find the dev tools to be as good of not better this time around. Curious which tools in particular you find worse? When was the last time you tried?
- _bxg1 7y ago
  You know, as I'm going back and trying to come up with specific points, I'm having a hard time. Partly it's little usability things: - There was one time when an HTTP request was failing and I couldn't figure out why, and in the Network tab Firefox wouldn't show any information about it, even the request that went out (other than the URL), whereas Chrome not only showed the headers, it surfaced that it was a 404. - There's no way to view all source files. You have to go to "Style Editor" for stylesheets and "Debugger" for JS files. I'm not sure how to view the other files that were loaded, outside of the Network tab. - I do enjoy how Chrome's inspector puts the box layout directly above the computed styles, instead of in a separate tab. Those all feel like nitpicks, though. It could just have more to do with me not being used to it. Maybe I haven't given it enough of a chance and should give it another try.
  - bogwog 7y ago
    FF's tools used to be pretty bad compared to Chrome's, and while my main browser has always been FF I always keep Chrome around for development purposes. Lately though I haven't found myself needing to switch over to Chrome for anything devtools related. This new replay feature makes FF even more compelling (once it comes to Linux that is). So if you haven't used FF for development recently, you should definitely give it a try.
    - _bxg1 7y ago
      My last try was pretty recent, but it was also brief
leevlad 7y ago
Curious to hear what's missing. I do some light front-end work (css/react) and have been fully on Firefox for about a year. Haven't looked back.
- somebodythere 7y ago
  For some reason I can't figure out how to place breakpoints at all in react/webpack code. I still switch to Chrome to do that.
SketchySeaBeast 7y ago
Do you use developer edition? The only thing that was missing from regular Firefox for me was web socket connections messages, and those are in the developer edition (and apparently coming soon to regular Firefox).
quickthrower2 7y ago
It might be that you are simply "used" to the chrome tools. I actually found FF doing better with typescript source maps ins some circumstances (e.g. resolving "this"), but to be fair sourcemaps are often problematic on both browsers.

by _bxg1 7y ago

udfalkso 7y ago

I recently switched back to FF after many years on chrome and find the dev tools to be as good of not better this time around. Curious which tools in particular you find worse? When was the last time you tried?

_bxg1 7y ago
You know, as I'm going back and trying to come up with specific points, I'm having a hard time. Partly it's little usability things: - There was one time when an HTTP request was failing and I couldn't figure out why, and in the Network tab Firefox wouldn't show any information about it, even the request that went out (other than the URL), whereas Chrome not only showed the headers, it surfaced that it was a 404. - There's no way to view all source files. You have to go to "Style Editor" for stylesheets and "Debugger" for JS files. I'm not sure how to view the other files that were loaded, outside of the Network tab. - I do enjoy how Chrome's inspector puts the box layout directly above the computed styles, instead of in a separate tab. Those all feel like nitpicks, though. It could just have more to do with me not being used to it. Maybe I haven't given it enough of a chance and should give it another try.
- bogwog 7y ago
  FF's tools used to be pretty bad compared to Chrome's, and while my main browser has always been FF I always keep Chrome around for development purposes. Lately though I haven't found myself needing to switch over to Chrome for anything devtools related. This new replay feature makes FF even more compelling (once it comes to Linux that is). So if you haven't used FF for development recently, you should definitely give it a try.
  - _bxg1 7y ago
    My last try was pretty recent, but it was also brief

leevlad 7y ago

Curious to hear what's missing. I do some light front-end work (css/react) and have been fully on Firefox for about a year. Haven't looked back.

somebodythere 7y ago
For some reason I can't figure out how to place breakpoints at all in react/webpack code. I still switch to Chrome to do that.

SketchySeaBeast 7y ago

Do you use developer edition? The only thing that was missing from regular Firefox for me was web socket connections messages, and those are in the developer edition (and apparently coming soon to regular Firefox).

quickthrower2 7y ago

It might be that you are simply "used" to the chrome tools. I actually found FF doing better with typescript source maps ins some circumstances (e.g. resolving "this"), but to be fair sourcemaps are often problematic on both browsers.