Earlier quoted context omitted.
The firebug theme in firefox dev tools has eased the pain somewhat for me.
Thanks for mentioning it! I still miss the Firebug, it just made more sense to me. For anyone searching for info how to enable the theme: https://developer.mozilla.org/en-US/docs/Tools/Settings
Saying Goodbye to Firebug
61–70 of 157 posts
Re: Saying Goodbye to Firebug
#62Firebug didn't just raise the bar for web debugging, it pretty much raised the bar for all debugging tools. It leaves a great legacy with the built-in dev tools. Great project.
I often argue that Firebug is the reason Firefox is still around. It was easier to develop on Firefox and then debug on IE. So a lot of websites worked on Firefox even if the management team didn't care (or even, in our case, when they told us not to support Firefox and we nodded and did it anyway)
Re: Saying Goodbye to Firebug
#63Firebug didn't just raise the bar for web debugging, it pretty much raised the bar for all debugging tools. It leaves a great legacy with the built-in dev tools. Great project.
I often argue that Firebug is the reason Firefox is still around. It was easier to develop on Firefox and then debug on IE. So a lot of websites worked on Firefox even if the management team didn't care (or even, in our case, when they told us not to support Firefox and we nodded and did it anyway)
Re: Saying Goodbye to Firebug
#64Earlier quoted context omitted.
> I absolutely abhor the network panel in Chrome. What do you mean? There are plenty of ways to filter down the activity tab in Chrome if the problem you're experiencing is that the volume of requests is too high to be useful.
I am more at home in FF so this might not be true for Chrome... Just look at the simplicity and elegance of Firebug net panel ( https://2r4s9p1yi1fa2jd7j43zph8r-wpengine.netdna-ssl.com/fil... ). I love Mozilla and respect them immensely, but any change they made to Firebug was for the worse. If they just copied the functionalities and design the result would be much better. I am very sorry I had to stop using Firebug…
Re: Saying Goodbye to Firebug
#65Firebug taught me css. I'll miss it. I hate the built in tool.
Re: Saying Goodbye to Firebug
#66Re: Saying Goodbye to Firebug
#67Re: Saying Goodbye to Firebug
#68Re: Saying Goodbye to Firebug
#69Does anyone know the history of the `console` object? The first time I ever saw it and used it was with Firebug, but it occurs to me that I don't know if Firebug invented it. Did it just decide to inject this name into the global namespace? And having it become a common API across multiple JS environments was due to its popularity in Firebug? Or was it somehow already in JS and I just wasn't aware of it up until that…
Here's console.js in 2007: https://github.com/firebug/firebug/blob/85f35d8e871783adcf9c...
Re: Saying Goodbye to Firebug
#70Things instantly became real when firebug for IE came out. To me that one tool made a front end web development career a viable option. Do y'all remember JS before Firebug? ouch
alert()