News for hackers. Stuff that matters.
Re:Why Rust? [pdf] by Manishearth on Wednesday September 09, 2015 @01:16PM (#10192674)
The first two are developer tools. It's fine to have to use nightly at dev time (better, in fact, due to compile time improvements!), and then ensure your build works on stable too.

Also, rustfmt is a binary which can work without nightly once you've compiled it.

Re:Why Rust? [pdf] by cm3 on Wednesday September 09, 2015 @01:37PM (#10192811)
Rust's users are all developers so there's no distinction between expert and novice users.

I built rustfmt with nightly Rust and it dynamically links all kinds of shared objects from the Rust install. This doesn't happen for a simple hello world so there must be something different in rustfmt's build.

Re:Why Rust? [pdf] by Manishearth on Wednesday September 09, 2015 @02:13PM (#10193074)
There is an important distinction when it comes to stability. Stability for libraries is much more important that stability for devtools

Stability mainly matters when you release a library and it stops working on a newer compiler, breaking everyone downstream. That's a pain for the downstream users, because they need not necessarily understand your library internals, and the software they're building will be completely broken until you update it.

If an optional developer tool breaks, it's only you that's affected, not downstream users. You can wait for it to be fixed, no problem.

Rustfmt uses internal Rust APIs to parse and reason about the code. It could use something else (like syntex), but that would be more work.

Re:Why Rust? [pdf] by cm3 on Wednesday September 09, 2015 @02:25PM (#10193169)
Can't rustfmt avoid dynamic linking?
Re:Why Rust? [pdf] by Manishearth on Wednesday September 09, 2015 @04:26PM (#10194310)
Actually, I'm surprised it does link dynamically, since Rust binaries are typically statically linked. But yes, it should be able to avoid that.