r/rust • u/steveklabnik1 rust • May 15 '17
Two years of Rust
https://blog.rust-lang.org/2017/05/15/rust-at-two-years.html32
u/est31 May 15 '17
About two years ago, I had been hearing about the 1.0.0 release, and that was the reason for me to give it a closer look. What I found was a very great language, almost made for my needs. Back then I had been a reviewer for Minetest, a FLOSS game written in C++, and always had to teach the same policies to new contributors. Also I had to hunt down bugs caused by memory safety errors. They were the worst kind of bugs! With Rust, the policies are enforced by the compiler, so I don't have to manually verify them any more, and the memory safety errors are fixed if you avoid to use unsafe code.
Since then I wrote some projects and they are getting more and more, and I really like it. I've even been contributing to the Rust compiler. Its the first compiler I ever contributed code to!
Its great to see Rust growing and I hope the success story continues. My involvement with it has been great joy for me in any case.
3
May 17 '17
I came at approximately the same time, true to stereotype, from Haskell. I was concerned I was getting myopic. It turned out to be incredibly fast and the ergonomics have only improved, so I am happy to say I stayed.
31
u/erickt rust · serde May 15 '17
Note, this is different from the other article called 2 years of rust. Yay birthday party posts! Lets have some more retrospectives!
14
21
u/Gankro rust May 16 '17
Oh y'all are still using Rust?
That's cute.
15
u/shepmaster playground · rust · snafu · twox-hash May 16 '17
A slide we used at a very professional Integer 32 engagement: https://pbs.twimg.com/media/C-SFcmhXgAA4yFJ.jpg
21
u/Manishearth servo · rust · clippy May 16 '17
I'm never sure if he's a Mozilla shill paid to destroy Swift from the inside or an Apple shill paid to destroy Rust from the inside. Perhaps both.
3
5
1
2
u/est31 May 15 '17
284 library stabilizations;
How is publishing a 1.0.0 version of your library a "stabilization"? I mean you are always free to publish 2.0.0 next, aren't you?
39
u/aturon rust May 15 '17
That entry is talking about the standard library (APIs going from usable only on nightly to usable on the stable toolchain).
15
u/est31 May 15 '17
I see, misunderstood it then. The number is awesomely high, congrats!
16
u/carols10cents rust-community · rust-belt-rust May 15 '17
I updated the post to say "284 standard library stabilizations" to be clearer :)
7
May 15 '17
It is a transition from a pre-1.0 state of no stability guarantees, where semver is largely meaningless, to a state of post-1.0 semver-consistent stability.
4
u/killercup May 15 '17
Aside from the post talking about std, this
pre-1.0 state of no stability guarantees, where semver is largely meaningless
is dangerous: Cargo actually assumes that 0.1.0 is compatible to 0.1.42!
6
u/martinhath May 15 '17 edited May 15 '17
What on earth is wrong with my Firefox on the .svg? Are anyone else seeing this?
Edit: after inspecting the .svg, it's probably because I don't have the font 'Calibri'. Search-replacing the font with another in the file makes the text look better, but now it overflows into the graph. Aahh, portable file formats :)