lastontheboat

Not right now. It's a huge amount of work to create something competitive, and as soon as you add a JIT you lose most of the safety benefits that Rust provides. There is js.rs (https://github.com/TomBebbington/js.rs) that already exists, however.

It actually suggests that we're misusing the trait in the short term, since it's one of the few that has built-in deriving magic in the compiler. In the future that won't be the case, but Rust is still a work in progress.

I don't know what this means, but we're totally implementing the DOM and JavaScript execution using SpiderMonkey.

http://rr-project.org/rr.html has all the gory details.

Correct.

Oh right, that's a special case. The Gecko HTML5 parser is already generated by a specially-targetted Java -> C++ translator. We want to use the same code and make it go Java -> Rust, that's all.

You're the best.

>plan to do auto conversion of C++ to Rust

This... is news to me? I'm pretty sure we have no such plans at all.

No, it's definitely still broken on 32bit platforms. It does not even finish building right now.

Nope. I mean, the parser's from there, but we're replacing it. We wrote a CSS parser to replace the NetSurf one we used for a bit, and all the layout code is from scratch. There's a Rust library called rust-http providing us with networking.

You might be interested in the ongoing reconstruction of Cave Story written in Rust: https://github.com/drbawb/rust-story

We've got lists of recommended contributions for newcomers, and they come with a mentor attached as well: http://www.joshmatthews.net/bugsahoy/

It's actually #introduction (no plural), but yes, we are a friendly bunch!

https://developer.mozilla.org/en-US/docs/Introduction#Step_5... should address the last question.

You have hit the problem on the head. I'm very interested in surfacing better information for potential new contributors, and these are all points that I've harped on before. There's an eternal tradeoff - things like wiki pages are easy to slap together, but just as easily can grow stale. Information that is retrieved from live databases is almost always better, but such dashboards can be complicated beasts to both build and make useful, especially with projects like Mozilla that are distributed among many different silos. Getting other people to care about keeping information relevant is another problem I face. So yeah, no solutions, just acknowledgement that you're right.

This sums up its status remarkably well.

We're definitely blurring the bounds of official-ness. Everybody in the organization who has seen it is always enthusiastic, and nobody has asked me to remove the tabzilla branding.

You should put together a Get Involved wiki page and submit a pull request.

You are absolutely correct. The domain doesn't match the content right now, but I'm going to be running a sprint to fill it out with non-coding-related activities soon. You can see a prototype at http://www.joshmatthews.net/asknot/; I'm mainly lacking experts who can provide me with content and links.

#2 is shipping as part of Firefox 20.