3 ms·

I have almost the opposite, I use chrome for browsing but find FF's dev tools a lot more intuitive. Different mindsets I guess, and while I do find that some FF

by eterm 11y ago

I have almost the opposite, I use chrome for browsing but find FF's dev tools a lot more intuitive. Different mindsets I guess, and while I do find that some FF debugging features are confusing (the difference between the console, the scratchpad and the GCLI is just an annoying distinction), overall I find FF has better console highlighting and is easier to browse objects because it'll expand a logged object to a sidebar on click, but in chrome it stays in that console. There is a separate issue where Firefox can have much worse performance when the developer tools are open. This is something has been slowly being addressed but I think there's still a lot of work to get it to chrome levels.

orf 11y ago
> overall I find FF has better console highlighting and is easier to browse objects because it'll expand a logged object to a sidebar on click I do actually like that feature, but in my experience the console is a lot less intuitive than the one in Chrome. I've pasted the output from running "$('a')" on github.com here[1] using both Chrome and Firefox. Firefox gives you a massive chunk of output that can't be minimized, while Chrome gives you a condensed output that you can actually navigate through (with pagination). It's annoying that outputting a large-ish object instantly destroys the log with way too much output. Stack traces are another annoyance, in Chrome I get a trace that I can minimize and maximize, with all the line numbers resolved using sourcemaps and with hyperlinks to the debugger. My experience with Firefox has been an unresolved giant minimized stacktrace that is really no fun to look at. The debugger also often just takes me to my concatenated 100000 line app.js file rather than using the sourcemaps. I guess it does come down to different mindsets, I've been playing with Firebug while writing this and it seems a lot better than I remember. I've also found this[2] post about them integrating Firebug into FF itself, so good things are on the horizon :) 1. http://paste.pound-python.org/show/lUuq1bnMzOnSbcl5bhvC/ http://paste.pound-python.org/show/lUuq1bnMzOnSbcl5bhvC/ 2. https://hacks.mozilla.org/2015/10/firebug-devtools-integration/ https://hacks.mozilla.org/2015/10/firebug-devtools-integrati...
- cpeterso 11y ago
  On the github.com home page, $('a') gives me the following in Firefox, with a nice attribute navigator panel: Object { length: 33, prevObject: Object, context: HTMLDocument → github.com, selector: "a", 33 more… } Chrome just spews a screenful of HTML to the console.
  - eterm 11y ago
    Another thing is that Firefox actually has a $ operator built in now, which is useful when the page does not even load jquery. (Chrome might have that as well?)

by eterm 11y ago

orf 11y ago

> overall I find FF has better console highlighting and is easier to browse objects because it'll expand a logged object to a sidebar on click I do actually like that feature, but in my experience the console is a lot less intuitive than the one in Chrome. I've pasted the output from running "$('a')" on github.com here[1] using both Chrome and Firefox. Firefox gives you a massive chunk of output that can't be minimized, while Chrome gives you a condensed output that you can actually navigate through (with pagination). It's annoying that outputting a large-ish object instantly destroys the log with way too much output. Stack traces are another annoyance, in Chrome I get a trace that I can minimize and maximize, with all the line numbers resolved using sourcemaps and with hyperlinks to the debugger. My experience with Firefox has been an unresolved giant minimized stacktrace that is really no fun to look at. The debugger also often just takes me to my concatenated 100000 line app.js file rather than using the sourcemaps. I guess it does come down to different mindsets, I've been playing with Firebug while writing this and it seems a lot better than I remember. I've also found this[2] post about them integrating Firebug into FF itself, so good things are on the horizon :) 1. http://paste.pound-python.org/show/lUuq1bnMzOnSbcl5bhvC/ http://paste.pound-python.org/show/lUuq1bnMzOnSbcl5bhvC/ 2. https://hacks.mozilla.org/2015/10/firebug-devtools-integration/ https://hacks.mozilla.org/2015/10/firebug-devtools-integrati...

cpeterso 11y ago
On the github.com home page, $('a') gives me the following in Firefox, with a nice attribute navigator panel: Object { length: 33, prevObject: Object, context: HTMLDocument → github.com, selector: "a", 33 more… } Chrome just spews a screenful of HTML to the console.
- eterm 11y ago
  Another thing is that Firefox actually has a $ operator built in now, which is useful when the page does not even load jquery. (Chrome might have that as well?)