I'm not sure it's wise to talk about Rust in those discussions, Rust is the language that needs nightly for a lot of recent libraries to work... talking about stability / backward compatibility.
It seems unlikely, if Rust's policies do a good job of maintaining guarantees in a chaotic environment like that, that they would fail in a more placid environment.
Whether Rust has some differences in its versioning, the situations are similar enough that I assert Rust's choices are relevant.
The fact that Rust itself may or may not have stability or backwards compatibility (I mean, I think it objectively does) isn't actually as important as the fact that the rust team wants to have those things and has thought hard about basically the same problem Go is tackling now, and has already taken the effort to write down its thoughts and conclusions.
If you want to claim I shouldn't bring up Rust's "editions" work, I'd rather you talk about the "editions" RFC rather than Rust's slightly different versioning scheme.
I use rust a lot, and it’s been heavily geared towards nightly for a long time.
The whole rust nightly/beta/stable hasnt worked well, because (afaik) the beta usage is tiny and people tend to jump on nightly or stable. It’s only very recently any effort has been made to change this for the new edition.
...so, you know, the comment may not be entirely accurate, sure, but it’s our fault people have come away from rust feeling that way.
The OP is not at fault here, and definitely not, I think, willfully lying.
Take a deep breath; there’s no need for this sort of attitude, and frankly it reflects badly on the rest of us (rust users).
My impression was that most people feel the Beta toolchain is doing its job just fine, because most projects that use CI include a Beta test run. I don't think the plan was ever to have people using Beta on the command line as their daily driver.
Notice specially the last month or so of actively asking people to try the beta.
If it wasn’t a problem, that wouldn’t be happening.
> Notice specially the last month or so of actively asking people to try the beta.
This is because for the last month the beta has represented the first release candidate for Rust 2018, which is more important than normal releases in all three of implementation scope, backwards compatibility concerns, and marketing potential.
Rocket requiring nightly is unfortunate, and I wish it didn't, but aside from Rocket stable has been a good forcing function to get crate authors to not add nightly dependencies.
Anyway, from what I see, actix seems to get more buzz than Rocket these days, precisely because the former works on stable.
It’s not like we’re past the nightly being the first toy people reach for to solve problems; that is still very much a thing.
Some crates will always require nightly because there will always be some people that want to take advantage of the latest features. That's a good thing to a degree, because it encourages experimentation with said features before stabilizing them. This is completely different from implying that nightly Rust is required by a lot of popular crates, which just isn't true. Most people are productively using stable Rust.
/shrug
The OPs point about some/many/[??? numbers of] people not using stable isn’t that unreasonable imo...
A year is a long time!
No, it doesn't.