It would be good if the core Rust team owned `rustfmt` the way the Go team owns their extremely opinionated format tool. It heavily enforces very consistent code formatting throughout all publicly available Go code.
Developers like to say they want choice when it comes to formatting, but take it away and you're left with resigned programmers who are very productive at reading code.
^^ Perhaps not the right outlet for this, but maybe you can point me to where this discussion is taking place.
Re:Why Rust? [pdf]
by steveklabnik on Wednesday September 09, 2015 @02:28PM
(#10193202)
Yes, our intent is to officially adopt rustfmt, and we expect that it will be widly used. It's just not ready yet. nrc, who's leading up the work, is a Mozilla employee, and in general, everyone wants it to be ready. Software just takes time :)
I also think that year-from-now Rust will be way nicer than at the moment, it's absolutely early days. But there's a lot you can do, even on stable, right now. This is why I said it depends on what you're doing. Some use cases have absolutely no choice but to use unstable things. Others have options, and others only use stable.
As to your three points:
1. You can configure things so that you only need nightly when doing benchmarking, and run on stable the rest of the time.
2. Compiling `rustfmt` needs nightly, but using it doesn't, as it's a binary.
3. Yeah, the SIMD stuff just happened, so it's gonna take some time.