121–130 of 157 posts
The inspector tool in Firebug was damn near instant to allow me to select an element in the browser. Firefox's version of the inspector can take upwards of 5 seconds sometimes to become "ready". Side note... I'm on a 7 year old macbook air, so the differences are very notable.
When I started out as a web developer 5 years ago, one of the prime reasons for choosing FF over chrome was Firebug. As a beginner, it made debugging so much easier. Five years later, I still cant fathom using anything but Firefox, alas, without firebug.
My memory might be way off base here, but I'm fairly sure Chrome Dev Tools were in a reasonable state by 2012. Screenshots from the time certainly suggest so. My experience is much the opposite, in that it was around 2012 or so that I probably stopped installing Firefox on my dev machines altogether. That said, recent features in Firefox (Containers especially) have me much more interested again.
By the time the Firefox 4 betas were out, it was no contest; Firebug was very crashy (which, to be fair, it's hard for an extension to support a beta browser, but Chrome's dev and beta channels always had a reasonably stable devtools thanks to it being built-in).
Earlier quoted context omitted.
Yeah, SoftICE, I remember buying Hackerzvoice (a French newspaper-like hacking magazine) which included SoftICE tutorials on how to crack WinRAR license verification. (for educational purposes of course) I was amazed that I could breakpoint and debug any running app. I miss SoftICE. I read this a while back from someone who work for the company which owns SoftICE copyright : https://reverseengineering.stackexchange.c…
Any idea what people use now instead of softice?
Earlier quoted context omitted.
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)
> It was easier to develop on Firefox and then debug on IE. A long time ago, the company I worked at had a website which worked only on IE, because it needed a specific ActiveX control for streaming video. But even though it would never work on Firefox, the developers still made as much of the site as possible work on Firefox, because whenever IE popped up an unhelpful error message ("Object expected" and others), re…
Does 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…
Firebug 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)
Earlier quoted context omitted.
It's definitely one of the weakest parts of the Firefox dev tools suite. I quite like Chrome's network panel though.
I consider Firefox's Network panel more useful than Chrome's. Having the ability to edit and resend network requests out of the box is exceptionally handy.
Earlier quoted context omitted.
I consider Firefox's Network panel more useful than Chrome's. Having the ability to edit and resend network requests out of the box is exceptionally handy.
On the other hand, having it always be a 2 step process kinda stinks. I haven't yet seen a way to just say "replay this request". The editing is nice, but I almost always have to just replay, quickly, and I can't do that in FF, but can in Chrome. Might be 20% of the time the 'edit and resend' is a handy/useful functionality - 'replay xhr' is handy the other 80% of the time.
Firebug was the greatest thing to happen to web development. Honestly I still prefer it to the native dev tools. I especially love how most things go to the console so I don't have to jump all over the place to find the information I'm looking for. I absolutely abhor the network panel in Chrome. It's like they're purposefully trying to make it difficult.
huh? How can one love firebug over Chrome Dev Tools? With the latter being just as revolutionary as firebug was when it first came out.
Earlier quoted context omitted.
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)
And now I would argue this is why everyone I work with uses Chrome for development. The debugging is superior.