canuckistani

No.

Sorry about that. Photon is a Design and User Experience refresh for Firefox 57, currently available in nightly builds.

( to be 100% crystal clear, I do think we'll ship things that use servo down the road )

Two things:

1. the largest part of the work on the "major rewrite" - do you mean quantum or servo? If the former, most of the bits we really care about will get shipped on Nov. 14th, and some other things like webrender will get shipped over the winter.

If you mean servo, you're right, that is a longer-term strategic project, but has recently provide useful as a source for innovation in Gecko with things like stylo and webrender, and especially Rust's capabilities as a language.

2. Mozilla is self-funded and has a very different governance model than perhaps you're used to - we are a US Corp ( and subsidiaries ) owned entirely by a US-based Not-for-profit.

That's true, we can't hire everywhere.

...and, yes there is a legacy problem with old code bases, but one trade-off for interns, contributors, junior developers is that you get to make an impact on a codebase used in a commercial project by hundreds of millions of people. Terrible tools written in anger in 2003 are still in use, sure, and terrible architectural decisions have been made, re-made, then made again over the years. It's the kind of messy any codebase eventually gets to.

This codebase still has life in it though, and the proof is in how far Gecko has come in the last year. Go run Nightly for a bit, compare it to Chrome or current Firefox. It's a big deal.

We are getting better at killing projects more quickly if they aren't working.

This isn't his main profile ( well I hope not any way ), it's a profile used to test extreme startup performance issues.

Here are two articles from last year articulating Mozilla's view on Firebug:

https://hacks.mozilla.org/2014/12/firebug-3-multiprocess-fir...

https://hacks.mozilla.org/2013/10/firefox-developer-tools-an...

https://hacks.mozilla.org/2013/10/firefox-developer-tools-an...

Platform support has landed in Firefox 44 and we're working on a prototype extension: https://github.com/firebug/websocket-monitor

Soon!

Thanks for voting - I agree this is a critical gap but I have high hopes to get it fixed very soon.

Jan Odvarko, the author of this post, is a Mozilla employee working on Firebug and related projects. He has worked for Mozilla for 4+ years and is paid to maintain / improve Firebug.

Which ones? Curious :)

Firebug takes over f12 from Devtools.

Ed: you should try ( and provide feedback to ) Firebug 3, they're dong exactly what you described - implementing Firebug UX on top of Firefox Devtools:

https://github.com/firebug/firebug.next

Man, that was 7 versions ago! WOuld love to get your impressions of Dev Edition 40. FYI it will create and use a separate profile from your main Firefox profile, so there is no risk in trying it out.

Safari on iOS is currently working for Mac & OS X, but we plan to ship and support Windows as well.

We have no plans to remove the tools from Firefox release.

I'm glad you got the reference.

That's correct, the devtools will remain in mainline Firefox ( source: I'm the PM ). We are starting to add in guards against things lke self-xss in mainline though, and dev edition will not have these sorts of things.

Thanks - we're definitely interested in Windows support and will take a look at this.

See also the profilist extension:

* https://addons.mozilla.org/en-US/firefox/addon/profilist

Hear, hear. None of this needs to be a standard to show a web page so I'm personally happy to let developers hack on what lets them be more productive, and let browsers continue to innovate. It's way too early to get a committee process involved, and innovation will happen faster this way.

There is the bug for nearly that exact thing:

https://bugzilla.mozilla.org/show_bug.cgi?id=890402

I linked to this comment in that bug, thanks for the feedback!

You can use console.dir to get an inline browse-able object, does that help?

See this screenshot:

http://note.io/HxSxmK

It depends on the device - each device has different hardware and may use proprietary drivers to access that hardware.