[bstar]

They should have been working on these issues a long time ago. I think they are far more important than many of the new features that came with v5. The only thing holding many of us back from using FF is the memory issue. Good thing the FB debugger is so awesome, because that's the only thing that keeps bringing me back at this point.

[benjiweber]

You imply there is a direct choice between working on one feature vs another. In reality not everyone can work on every aspect of a project. Plus it's a free software project. Contributors will work on whatever is important to them/their company.

[chaud]

Amusingly enough, Firebug has significant memory usage/leak issues and most users are much better off using it in another profile to keep down memory usage.

[erikb]

So true. Getting the speed up again is a major feature, it can't be delayed so long. FF4 already disappointed a lot in actually working a lot slower (on my machines, at least). So slow that I had to switch to Chrome, actually.

I didn't know what went wrong in their meetings, but not focusing on speed definitely was one of the worst decisions, they could have made. I hope they don't continue making big mistakes like that.

[beck5]

Is FB better than chrome dev tools?

[MattJ100]

I use both. I find that sometimes one or the other will display some weird traceback, or worse, silently fail. Now my first reaction to a problem that isn't obvious is to switch debugger.

Sadly I think the world of Javascript debugging still has some way to go...

[bstar]

For me FB is better for prototypin code. You have the expanded console that allows me to write code quickly on pages that I may not have direct access to (like production pages). I feel like I'm using a text editor. Webkit debugger is much more limited in this regard.

[LukeShu]

IMO, yes. Maybe it's that I was on Chromium on GNU/Linux, and not Chrome proper, but I found the chrome dev tools to be buggy, and a little incomplete, like as-of-yet unpolished FB clone.