4 ms·

> Plus working in chrome dev tools all day long, you really miss it when you want to pop something open and look under the hood real quick, and I don't think Fi

> Plus working in chrome dev tools all day long, you really miss it when you want to pop something open and look under the hood real quick, and I don't think Firefox is quite up to par there Based on what? What did you try to do and couldn't? Or is your complaint - like the rest of your comment says - that you weren't immediately familiar with the UI, you didn't bother learning, and then decided it was the browser's fault? How long did it take originally for you to learn the Chrome tools and how long have you given Firefox?

Klonoar 8y ago
Protip: when you want to sell someone on something, a response of "you're doing it wrong, you're the problem" generally doesn't work. It's a pretty widely held thing that FF's dev tools don't feel as smooth or well thought out as Chrome's, which is frustrating because FF (really, FireBug, unless you count the weird IE stuff) pretty much _made_ the concept of browser tools great. I'd love to use FF again too, but for me the blocker is the UI and battery drain. 's why I just use Safari.
- calcifer 8y ago
  > Protip: when you want to sell someone on something, a response of "you're doing it wrong, you're the problem" generally doesn't work. I agree, but how is this relevant to my comment? I didn't say the GP did anything wrong - I asked them what they did. Not nearly the same thing. > It's a pretty widely held thing that FF's dev tools don't feel as smooth or well thought out as Chrome's There are a large number of groups with widely held beliefs where said beliefs don't stand up to scrutiny. "It doesn't feel like Chrome" is not a belief that doubles as valid criticism because it's not actionable. Its sole purpose is to complain about things while making sure nobody can ever act on them because it's so vague. > for me the blocker is the UI and battery drain While "the UI" fits in to the category above, battery drain is an actual, specific, measurable and actionable complaint. So please, more of the latter, less of the former.
danShumway 8y ago
Stack rewinding, code editing/saving, breakpoints on DOM subtree and attribute modifications, the ability to search for requests via response text (very useful when reverse-engineering APIs), breakpoints on XHR requests, event listener breakpoints. These are not things that Firefox just does differently, they're features that Firefox just doesn't have. Firefox's dev tools aren't bad in and of themselves. The UX is fine, and getting better. I don't know if other people have opinions about memory tools or profiling -- I don't all that much. I guess Firefox's dev tools look prettier, and they do have some features that Chrome doesn't. But Firefox features tend to trend more towards, "here's a cool thing like the ability to debug shaders". Chrome's trend more towards, "here's a useful thing like the ability to debug Javascript."

Klonoar 8y ago

Protip: when you want to sell someone on something, a response of "you're doing it wrong, you're the problem" generally doesn't work. It's a pretty widely held thing that FF's dev tools don't feel as smooth or well thought out as Chrome's, which is frustrating because FF (really, FireBug, unless you count the weird IE stuff) pretty much _made_ the concept of browser tools great. I'd love to use FF again too, but for me the blocker is the UI and battery drain. 's why I just use Safari.

calcifer 8y ago
> Protip: when you want to sell someone on something, a response of "you're doing it wrong, you're the problem" generally doesn't work. I agree, but how is this relevant to my comment? I didn't say the GP did anything wrong - I asked them what they did. Not nearly the same thing. > It's a pretty widely held thing that FF's dev tools don't feel as smooth or well thought out as Chrome's There are a large number of groups with widely held beliefs where said beliefs don't stand up to scrutiny. "It doesn't feel like Chrome" is not a belief that doubles as valid criticism because it's not actionable. Its sole purpose is to complain about things while making sure nobody can ever act on them because it's so vague. > for me the blocker is the UI and battery drain While "the UI" fits in to the category above, battery drain is an actual, specific, measurable and actionable complaint. So please, more of the latter, less of the former.

danShumway 8y ago

Stack rewinding, code editing/saving, breakpoints on DOM subtree and attribute modifications, the ability to search for requests via response text (very useful when reverse-engineering APIs), breakpoints on XHR requests, event listener breakpoints. These are not things that Firefox just does differently, they're features that Firefox just doesn't have. Firefox's dev tools aren't bad in and of themselves. The UX is fine, and getting better. I don't know if other people have opinions about memory tools or profiling -- I don't all that much. I guess Firefox's dev tools look prettier, and they do have some features that Chrome doesn't. But Firefox features tend to trend more towards, "here's a cool thing like the ability to debug shaders". Chrome's trend more towards, "here's a useful thing like the ability to debug Javascript."