21–30 of 123 posts
I used to use Firebug extensively. These days, the built-in Firefox developer tools seem to cover everything I need.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
I really need to stop being so dependent on Firebug. I've done coding sessions or interviews where the other developer only has Google Chrome. Since I use Firebug so much, I am not as proficient with Chrome Dev tools. It makes me look like an amateur when I fumble around. Half the time saying I am used to Firebug is useless since they don't even know what it is.
So what if you are the black sheep of the shed?
I really need to stop being so dependent on Firebug. I've done coding sessions or interviews where the other developer only has Google Chrome. Since I use Firebug so much, I am not as proficient with Chrome Dev tools. It makes me look like an amateur when I fumble around. Half the time saying I am used to Firebug is useless since they don't even know what it is.
So what if you are the black sheep of the shed?
I used to use Firebug extensively. These days, the built-in Firefox developer tools seem to cover everything I need.
Same here. Can any current Firebug users comment as to what they like about it over the built-in tools?
I liked firbugs javascript debugger a bit better. Firefox has been updating the tools alot lately though and I like them. Though sometimes they tend to flake out (javascript debugger blowing over breakpoints until restart...).
I'll give the new firebug a try.
I really need to stop being so dependent on Firebug. I've done coding sessions or interviews where the other developer only has Google Chrome. Since I use Firebug so much, I am not as proficient with Chrome Dev tools. It makes me look like an amateur when I fumble around. Half the time saying I am used to Firebug is useless since they don't even know what it is.
So what if you are the black sheep of the shed?
Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.
I'm always surprised when I read comments about how the Firefox devtools offer the best developer experience. Every single one of these new features (except searching the dom via CSS selectors or regex) have been available in Safari's Web Inspector for OS X for at least a year. Plus, I think the UI is more thought out and easy to use in Safari. Can someone explain what Safari's Web Inspector is lacking?
It has a platform limitation.
I wish Firebug had proper JS stack trace. I find Chrome/Webkit's implementation essential for debugging.
Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.
I'm always surprised when I read comments about how the Firefox devtools offer the best developer experience. Every single one of these new features (except searching the dom via CSS selectors or regex) have been available in Safari's Web Inspector for OS X for at least a year. Plus, I think the UI is more thought out and easy to use in Safari. Can someone explain what Safari's Web Inspector is lacking?
Only issue I have is the fact it changes more or less every release, leading to a day or so of re-learning how to do certain tasks.
Does Safari support source-maps yet?