@campd
Like pcwalton said, we already use Gecko to render the UI. But we're using a less well-optimized, less well-maintained corner of Gecko. Improving performance is an explicit goal of this work.
It's not not the first step. That's not the primary driver of this plan. But it might be a happy side effect. Servo is still in early stages, we aren't making product plans around it.
console.mihai() is in at least Nightly and Developer Edition so far. It doesn't tab complete, and it's not available from content. Mihai didn't like too much attention ;)
This is a thing, on Firefox Nightly or Developer Edition.
And that work is key to the stuff we're doing. Thanks again, Chrome folks!
Integration with external editors/IDEs is a very important part of this project. A lot of what WebIDE brings to the party on top of normal editing is device/simulator management as well as the usual Developer Tools…
Resource usage of devtools that aren't running is near zero (there's a tiny bit of overhead to manage the menu items to launch it). Download size is affected, although for larger parts of the developer tools (things…
The team here is dedicated to developer tools full-time. We have no intention of slowing down.
https://hacks.mozilla.org/2013/10/firefox-developer-tools-an... has the current description of that relationship.
> To be quite frank, this is really ridiculous to me. Why in heck are there TWO separate developer tools for one browser that are both in-house? I tried to clarify this in another comment:…
Jan Odvarko, the current maintainer of Firebug, is on our team. He's currently the only Mozilla employee dedicated to the Firebug project. He's joined by a healthy community (you can follow the project at…
> > An intelligent debugger that would automatically step over certain files > That's interesting. I never thought about this. I like that. You haven't been reading your mail, paul! We discussed this briefly…
Like pcwalton said, we already use Gecko to render the UI. But we're using a less well-optimized, less well-maintained corner of Gecko. Improving performance is an explicit goal of this work.
It's not not the first step. That's not the primary driver of this plan. But it might be a happy side effect. Servo is still in early stages, we aren't making product plans around it.
console.mihai() is in at least Nightly and Developer Edition so far. It doesn't tab complete, and it's not available from content. Mihai didn't like too much attention ;)
This is a thing, on Firefox Nightly or Developer Edition.
And that work is key to the stuff we're doing. Thanks again, Chrome folks!
Integration with external editors/IDEs is a very important part of this project. A lot of what WebIDE brings to the party on top of normal editing is device/simulator management as well as the usual Developer Tools…
Resource usage of devtools that aren't running is near zero (there's a tiny bit of overhead to manage the menu items to launch it). Download size is affected, although for larger parts of the developer tools (things…
The team here is dedicated to developer tools full-time. We have no intention of slowing down.
https://hacks.mozilla.org/2013/10/firefox-developer-tools-an... has the current description of that relationship.
> To be quite frank, this is really ridiculous to me. Why in heck are there TWO separate developer tools for one browser that are both in-house? I tried to clarify this in another comment:…
Jan Odvarko, the current maintainer of Firebug, is on our team. He's currently the only Mozilla employee dedicated to the Firebug project. He's joined by a healthy community (you can follow the project at…
> > An intelligent debugger that would automatically step over certain files > That's interesting. I never thought about this. I like that. You haven't been reading your mail, paul! We discussed this briefly…