Hacker News Reader

Comment by pinpoll | Hacker News Reader

Still, I prefer Firebug. Is it fully supported yet?

Firebug can't hook into stuff that the built-in tools can mostly because the built-in tools are inside the browser itself and Firebug is an add-on.

I don't recommend using it any longer...

That is not true. I am sure add-ons can access the same stuff that built-in tools can. Most of the stuff are exposed as JS objects and there are APIs for a lot of stuff. APIs for devtools may be a bit hard to find the documentation sometimes. I guess it is because it is still being developed.

https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/...

Firebug 3.0 will be built on top of the native developer tools

https://getfirebug.com/wiki/index.php/Firebug.next

Could you please provide some decent examples that would convince a Firebug fan from the beginning to uninstall it? :)

For me Firebug seems ~2x as slow (eg, for a 1s operation in native tools, firebug takes 2s). Opening Firebug on my workstation causes a noticable pause in all activity on page for several seconds, while opening the native tools only takes about half a second. All of Firefox's dev tools are still a ways from being as fast and bug-free as the Webkit tools (both Chrome and Safari). I can't cite specific examples since I dropped Firebug in Firefox once the native tools reached a certain level of quality. I just suggest trying to use 'em and seeing if you like them more than Firebug. I did.

Speed is a good point, I'll give the native tools in FF 31.0 a try. Moreover, I'm curious if the built-in profiler is any good as YSlow for Firebug?

Btw, here's a discussion that I found to be interesting as well: http://stackoverflow.com/questions/19180494/which-advantages...

I have a little bit of a hard time believing this: Firefox Addons can use almost all the APIs in the browser that built-in code can, and I'm at least led to believe the new debugging APIs the built-in tools are using are no exception to that rule. https://developer.mozilla.org/en-US/docs/Tools/Debugger-API seems to agree on those points. Or do you mean the tools themselves aren't extensible?

It's been a few years since I've written any Firefox code or touched XPCOM, so I could be looking on this without up-to-date information: I'd be interested if the Firebug authors or others have written any thoughts on struggles they have with this.

I moved from firebug like a year ago but I really miss some firebug's pluggins; like jquerify or the ace integration ..

is there something similar for the built-in console?

Reply on news.ycombinator.com