31–40 of 79 posts
Granted, I really wanted to donate until I saw they used Paypal. Lots of other options now guys: https://www.wepay.com/ https://payments.amazon.com/sdui/sdui/index.htm
Maybe someone will read this and consider it for the future. I'd donate $50 today if I could do so via Amazon payments.
With no doubt, the Firebug team can take credit for changing the world of Web development. These guys aren't giving themselves enough credit. IMO, they can take credit for advancing the world of Web development. While the other development tools are (quickly) catching up, firebug is still leading the pack.
I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.
Have you tried the add-ons Vimperator + "Tree Style Tab" (remember to activate "Auto hide tab bar")?
With no doubt, the Firebug team can take credit for changing the world of Web development. These guys aren't giving themselves enough credit. IMO, they can take credit for advancing the world of Web development. While the other development tools are (quickly) catching up, firebug is still leading the pack.
I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.
I'm happy I've made the switch, though it would be nice if Chrome/webkit traded some flashy icons for a more space efficient table especially in the "Resources" tab.
I would love to see a JavaScript debugger that could break to something like an ipython shell. It's the one thing I really miss moving from server side to client side debugging.
Earlier quoted context omitted.
> but firebug blows chrome's debugger out of the water. Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?
Yeah, I'd also like to see an analysis of this. I used to be an automatic 'switch to Firefox for debugging' user, but I find that the Chrome developer tools are now pretty sufficient.
I develop exclusively in Firefox, and test on other browsers, so I use Firebug all the time. How well do other built-in tools compare to it?
I can only speak for the Chrome/Safari WebInspector, and they're good, but I find myself going back to Firebug if I have to do any serious debugging - personally I find there to be a big step up in usability with Firebug meaning I can work faster. It'll be interesting to see what happens to development tools when Firebug goes cross-browser.
Frankly, I haven't dug too deep into the economics of Firebug, but I hold the assumption that the project is not financially motivated. It's a typical open project where the developers' reward is the process of creative problem solving and also giving back to the community.
When financial reward is not the goal, my first thought would be to work with and not against the browser developers. There is a common goal so why not focus resources.
I'm glad that that is not the case because it is this competition, financial or not, that drives innovation.
I'm looking forward to learning more about the motivations behind FB since I use it almost daily. My preliminary quest didn't get too far since the footer link points to a parked (squatted) site.
Earlier quoted context omitted.
Personally I browse in Chrome, but the second I start debugging JS/AJAX i'll open Firefox and use that. It's 10x slower, it has Memory leaks up the wazoo, but firebug blows chrome's debugger out of the water.
> but firebug blows chrome's debugger out of the water. Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?
That said, I do most of my debugging in Chrome, only switching to Firefox/Firebug when they fail me, which isn't too often.