Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Saying Goodbye to Firebug

hacks.mozilla.org

Post reply on HN
Print view View original

151–157 of 157 posts

Re: Saying Goodbye to Firebug

#151

Post by ams6110 »

masklinn wrote: post #83
emehrkay wrote: post #9

Things 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

> Do y'all remember JS before Firebug? ouch Most people debugged with alerts or document.write-ing in the page. The "wokest" were aware of Venkman (Moz/FF), Script Editor (IE) and the Visual Studio IE integration (also IE), all of which were pretty much just JS debuggers. Venkman worked the best but the UX was a horrendous mess, SE and VS were less visually messy but (likely due to IE) frequently got lost entirely an…

Heh I still debug JS mostly with alert() calls.

Re: Saying Goodbye to Firebug

#152

Post by cup-of-tea »

irrational wrote: post #7

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.

It really was. I actually quit web development a few months before I learnt about Firebug because Internet Explorer was causing me loss of sleep (seriously). When I discovered Firebug I almost wanted to start doing it again, but then I quickly reminded myself that it wouldn't help with IE6 retardation.

I was really surprised to see an inferior clone appear in Chrome. I then started to hear people talking about Chrome dev tools and would always ask, "did you not know about Firebug?", and the answer would be no. Strange.

Re: Saying Goodbye to Firebug

#153

Post by mistercow »

ZenoArrow wrote: post #130
qudat wrote: post #126

Earlier quoted context omitted.

And now I would argue this is why everyone I work with uses Chrome for development. The debugging is superior.

Superior in what way? I suspect it's more a case of what you're familiar with rather than something which is clearly superior.

Does FF or Firebug have a way to override assets with a local directory? I haven't found it, and that alone makes my debug cycles a lot slower if I'm editing CSS.

Re: Saying Goodbye to Firebug

#154

Post by jordache »

masklinn wrote: post #140
pvdebbe wrote: post #134

Earlier quoted context omitted.

I think revolutionary as how Apple defines the word. They weren't the first but they sure had the panels running the smoothest.

That makes no sense, GP stated the chrome devtools were just as revolutionary as firebug was when it first came out . Not just "meaninglessly revolutionary" but more revolutionary than the one tool at the origin of all modern web devtools .

I don't remember precisely the feature set of Chrome devtools in intial version. I should have clarified. The current iteration of Chrome Devtools compared to firebug represents a revolution in web debugging capability

Re: Saying Goodbye to Firebug

#155

Post by masklinn »

ams6110 wrote: post #151
masklinn wrote: post #83

Earlier quoted context omitted.

> Do y'all remember JS before Firebug? ouch Most people debugged with alerts or document.write-ing in the page. The "wokest" were aware of Venkman (Moz/FF), Script Editor (IE) and the Visual Studio IE integration (also IE), all of which were pretty much just JS debuggers. Venkman worked the best but the UX was a horrendous mess, SE and VS were less visually messy but (likely due to IE) frequently got lost entirely an…

Heh I still debug JS mostly with alert() calls.

But… why?

Re: Saying Goodbye to Firebug

#157

Post by ZenoArrow »

mistercow wrote: post #153
ZenoArrow wrote: post #130

Earlier quoted context omitted.

Superior in what way? I suspect it's more a case of what you're familiar with rather than something which is clearly superior.

Does FF or Firebug have a way to override assets with a local directory? I haven't found it, and that alone makes my debug cycles a lot slower if I'm editing CSS.

If you're talking about CSS in particular, you can import existing CSS documents using an option in the Stylesheet Editor tab.
Post reply on HN