The only differences that come to my mind are super minor (chrome logging 400er requests to console, Firefox having more advanced grid/flex debugging. I'm kinda interested if I'm missing a super obvious feature that's commonly used.
The only differences that come to my mind are super minor (chrome logging 400er requests to console, Firefox having more advanced grid/flex debugging. I'm kinda interested if I'm missing a super obvious feature that's commonly used.
It's also a psychological bond to a certain extent, having relied on them during stressful times in my career... before that I had only FireBug and that served a similar purpose but didn't teach me quite as well and did never reach the status of "if the Chrome Devtools are open, I can understand what's going on here"-sense of security & confidence.
Overall, it also seems less accessible to me. It may well be that it's much more powerful in some respects, but I've never got my head around it enough to work that out.
I do very much rate its Memory Tree Map view, though. Big advantage over Chrome for rapid debugging of where memory goes.
Sometimes stack traces are missing in the console which Chrome does show.