4 ms·
> Rust is a young language and I would be pleasantly surprised to see code written today still compile in five years. We have had a code stability promise for
by pcwalton 11y ago
> Rust is a young language and I would be pleasantly surprised to see code written today still compile in five years.
We have had a code stability promise for months now in 1.0. So what you are saying here is that you do not believe that Rust will adhere to what it very publicly planned to do. Do you have specific reasons for this?
> To me, the big questions are what will happen to Rust if Mozilla changes strategies (Persona, Thunderbird, FirefoxOS) and whether Mozilla will continue to be a successful organisation.
Rust has a core team and community that overlaps a lot with, but is very much not identical to, Mozilla. Probably most Rust users aren't even Firefox users.
Rust is not "Mozilla's language". It's the Rust community's language.
- blub 11y agoMy only reason is that experience and surprising developments have made me into a skeptic when discussing technology. I was not aware of any promises.
- x0x0 11y agoAre there any large deployments of Rust outside Mozilla? (I'm not being sarcastic, just wondering who with resources besides Mozilla is incentivized to put money into Rust development.) Thanks!
- steveklabnik 11y agoThe largest is currently Dropbox, who re-wrote the way they store the bytes on disk in Rust. It was deployed in late December, they have promised a report after it's been in production longer than a few weeks.
- x0x0 11y agothank you; I'll put a note on my calendar to check in a couple weeks edit: Once you google for dropbox rust, you find some really interesting stuff; here's an overview https://news.ycombinator.com/item?id=9724849 https://news.ycombinator.com/item?id=9724849
- kibwen 11y agoAuthor of that comment here, let me update it with some new links for you. :) Putting Rust into production at Dropbox: https://www.reddit.com/r/rust/comments/3wrgl0/what_are_you_folks_working_on_this_week_512015/cy0abj2 https://www.reddit.com/r/rust/comments/3wrgl0/what_are_you_f... Some preliminary feedback on using Rust at Dropbox: https://www.reddit.com/r/programming/comments/3w8dgn/announcing_rust_15/cxucrse https://www.reddit.com/r/programming/comments/3w8dgn/announc...
- comex 11y ago> We have had a code stability promise for months now in 1.0. So what you are saying here is that you do not believe that Rust will adhere to what it very publicly planned to do. Do you have specific reasons for this? Since 1.0, Rust has in fact had multiple significant stable-breaking compiler changes, not to mention that, among other things, adding any new method to a trait or type in the standard library has the potential to cause breakage. The official code stability promise has not been violated by these changes only because it's riddled with exceptions.
- steveklabnik 11y agoI don't think this phrasing is particularly charitable, yet we don't need to argue about semantics, because we have numbers. > Approximately 96% of published crate revisions that build with the 1.0 compiler > build with the 1.5 compiler. https://internals.rust-lang.org/t/rust-regressions-2015-year-end-report/2993 https://internals.rust-lang.org/t/rust-regressions-2015-year...
- comex 11y agoI've seen it, and if that rate of 4% of code breaking in half a year were to continue, in the above stipulated 5 years it would look pretty bad. Hopefully it will not, given that some of those regressions involved soundness issues and other things (integer fallback) that were "clearly wrong", which ought to be mostly weeded out before long. That said, the rate of new features in the language and especially libraries seems likely to increase a bit in the nearish features, given the size of the feature request backlog (or not - you'd know better than I). But even at a rate of significantly less than 4%, there's still trouble. That figure is based on the number of root regressions, right? (If I'm wrong, disregard the rest of this paragraph, but I don't think so...) That is, the number of crates that break on their own accord, rather than those that won't compile because one of their dependencies is broken. If one application depends on dozens of crates (or is just really large), the chances of it breaking somewhere are much higher. This can be partially mitigated by the crates themselves releasing upgrades, but look at Python 3 - there will eventually be a lot of code out there that's completely unmaintained, especially within the "dark matter" of internal or closed source applications. Also, a fix in the latest version of a crate will probably not be backported to long deprecated major versions of it - which means that if I dust off a crate that hasn't been touched in years and uses such a version, I'd have to either upgrade the dependency or do the backport manually. And the ancestor post did say five years: last I checked on the lists, there was no real consensus as to when Rust 2.0 should be released, on a scale from "in a year" to "never". Maybe there is more consensus internally, but I'd be surprised if it didn't happen in that long... edit: It's not an entirely fair comparison, but for what my ideal stability promise for a programming language would look like, one need not look very far - only as far as Mozilla's other programming language.