Live data from Hacker News

Saying Goodbye to Firebug

hacks.mozilla.org

71–80 of 157 posts

Re: Saying Goodbye to Firebug

#71

edit: wldcordeiro pointed to a UI that looks nothing like what I have as a UI (in Firefox 56)... removing my comment until I can figure out why. edit edit: Apparently the last time I tried to install Firebug it instead asked me to just make Developer Tools look like Firebug, which is definitely a bad idea.

The modern Firefox Debugger has none of the issues you're whining about.

https://github.com/devtools-html/debugger.html

Re: Saying Goodbye to Firebug

#72

For those that have made the switch in the Firefox Developer era, do you find the developer tools as good as Chrome's? In the last week I've made the switch back to Firefox (Developer) and it's been awesome. I haven't had done any front end work yet so I haven't used the developer tools, though. I never really cared for the ergonomics of the Chrome devtools but I was really familiar with them and could efficiently pr…

They trade off. I think I still prefer the Chrome performance and memory tools but the inspector, debugger and most other tools I prefer in Firefox.

Re: Saying Goodbye to Firebug

#73
post #10

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.

The firebug theme in firefox dev tools has eased the pain somewhat for me.

That theme is so ugly. It's like Firebug is permanently stuck in Windows XP.

Re: Saying Goodbye to Firebug

#74
RIP Firebug, brings back great memories of learning HTML / CSS / XPath selectors. I use Chrome developer tools these days (not a huge fan but it does work) but Firebug will always have a special place in my heart as a GREAT debugging tool.

Re: Saying Goodbye to Firebug

#75

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.

> 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.

It is interesting that Network Panel in Firefox has built-in simple Postman-like tool [1] for editing request which you have already made.

[1]: https://imgur.com/a/hBkmq

// Chrome has copy as curl command.

Re: Saying Goodbye to Firebug

#76

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?

It depends on what you are trying to do. Softice was good for "kernel" debugging, rather than just simple user space programs for which things like turbo debugger (and more modern solutions), were as good if not better.

For windows kernel debugging, there is windbg, kd, and assorted "emulation" methods like qemu's gdb stub. Similarly for linux/kgdb/etc... OTOH, Softice had a number of OS data structure aware commands in the late 1990's which are only really available in something like windbg. In theory you could write kgdb macro's to perform most of that functionality for linux/etc but it doesn't work out of the box.

Although in the end, the logical replacement for softIce, is a JTAG debugger of some form. A fair number of the ARM platforms work with DS5/Dstream which provides source level debugging with far more functionality (for example trace level timing information) than softice as an "ICE' ever did. I guess its the same for intel's ITP-XDP3/system studio products these days.

Again, it depends on what your trying to debug. AKA do you need the "ICE' (aka JTAG these days) functionality, or are you just looking for a powerful kernel or user-space debugger.

Re: Saying Goodbye to Firebug

#78
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

alert()

Which didn't help much when there was a syntax error somewhere close by causing the browser to silently terminate parsing/executing the code. At least these days the browsers tend to dump error messages into the console when this happens...

In theory that could have been caught by a good jslint/syntax checker but those were a few years in the future too. Early, JS development really sucked, its only slightly better today..

Re: Saying Goodbye to Firebug

#79

Earlier 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.

It is interesting that Network Panel in Firefox has built-in simple Postman-like tool [1] for editing request which you have already made. [1]: https://imgur.com/a/hBkmq // Chrome has copy as curl command.

// firefox has copy as curl too, fwiw

but yeah, the edit-and-resend tool is amazing

Post reply on HN