I too am not affiliated to Mozilla, unless the browser I'm using makes me an affiliated member. However judging from their discussion group, they know it's a problem and will probably try to reduce it to 15min(this is their goal, not their achieved min speed). Sadly, speed of compilation probably won't beat Go's which is 2min.

I do understand your complaint, but dismissing an alpha language because it compilation is too long, or documentation isn't up to par is a bit of an overstretch. They haven't been optimizing for it and the syntax is shifting, so making documentation at this point is like building a house on a sand pit.

This is unfair.

Rust still builds LLVM toolchain (all of it!) to bootstrap itself.

As far as I know, they are planning to remove this dependency before Rust gets to 1.0.

They're having to use a custom version of LLVM (for GC reasons, I think) but havent yet got the patches back into the upstream mainline (but are presumably planning to).

Hah, all sane modern languages needs to patch LLVM for GC reasons :) The guys writing it did not really know a lot about that area and how to get those intrinsic features into the LLVM proper.

Are "the guys" the LLVM people or the Rust implementers?

I imagine the LLVM people.

If you look at the LLVM documentation there is still a lot to do to be able to support most performant GC algorithms.

Congrats, you encountered my first complaint with Rust. Let me know how much fun the out-of-date documentation referencing syntax that no longer exists is.

If you ask about it or seek a redress you'll be told, "we're not reeeaaaaaady".

It's a state of affairs they've come to be quite comfortable with.

You're supposed to use Rust unless you're a Mozilla employee or intern, afaict.

What do you expect? They aren't ready.

I'm following the development of Rust with much interest. The design seems well-thought out, and occasional comments here by 'pcwalton, usually along the lines of “here's how we're trying to solve this problem in Rust”, are always worth a read. I wouldn't start a project in it, however, for at least another year unless my main goal was to experiment with the language.

When I did play with it a little, I indeed ran into problems with out-of-date documentation, but someone in #rust IRC (I think it was 'brson) very helpfully answered my questions and pointed me to some newer docs.

Perhaps your expectations are unrealistic. If you want a language you can use today for a real project, try Clojure or Go. I don't think you can fault the Rust project for being where they are now and communicating honestly.

Maybe you just shouldn't use it now when it's not ready. There is no reason to complain about missing documentation or other stuff if they didn't get to do it until now. That what "not ready" means. Keep calm and wait ;-)