8 ms·
I would like to take this opportunity to formally apologize to the HN community for that time back in early 2012 when I predicted that Rust 1.0 would be release
by kibwen 12y ago
I would like to take this opportunity to formally apologize to the HN community for that time back in early 2012 when I predicted that Rust 1.0 would be released "in about six months or so", and later proceeded to proudly proclaim that 0.4 would be the last release with major breaking changes to the syntax. I hope you all can find it in your hearts to forgive me. :) But at long last, we did it, and it's almost too good to believe.
But as much work as it's been just to get to this point, the real struggle begins today. Months and years of brutal campaigning, compiler engineering, and careful language design lie ahead. If you've yet to take a look at Rust, please do, and report your findings so that we can better prioritize our efforts for the near future. If you like what you see, there's plenty of work to go around and a welcoming community should you decide to dig in and join us. And if you don't like what you see, that's fine too; Rust is not the language to end all languages! We're just here to make the world a little safer, however we can. Hopefully today is but the first page in that story. :)
- drbawb 12y agoIt seems like just yesterday I was getting all misty-eyed over losing my friend the `~` sigil. rust-story builds on 1.0, though, so I think I'll be able to forgive you. ;^) Congrats on the release!
- barosl 12y agoThat's funny, because I started hacking Rust just because the `~` sigil and friends were gone. :-) Before that, so many sigils in Rust scared me and kept me from learning it. Rust still has a bit many sigils nowadays, but it's definitely cleaner than before!
- drbawb 12y ago>so many sigils in Rust scared me and kept me from learning it. I had just started seriously learning rust a few months before they started moving owned pointers into `std`. So I felt somewhat betrayed by the removal of the sigils. It seemed like all the hard work I had spent learning the various pointer types would end up being useless! Of course that fear was ungrounded. I very quickly came to understand that what I had actually spent time learning was ownership; and _that knowledge_ is still perfectly relevant, even today in rust 1.0. All that was really changing was the removal of some arcane syntax which had only served as a stumbling block in my quest to learn Rust.
- sho_hn 12y ago> It seemed like all the hard work I had spent learning the various pointer types would end up being useless! I always joke about this being "programmer Stockholm syndrome": When you've mastered something that's actually not good at all, don't want that time and effort to have been for nothing, and become a champion for crap. It happens a lot and usually unintentionally - the champion feels genuine joy about the intricacies of what they're pushing and just wants to share it with others. You can see this happening a lot around poorly thought-through and/or overly complex technologies. This is why Rust's progressive trimming and slimming over the last 1-2 years has been really impressive and gratifying to watch - it really takes a lot to reevaluate and let go. Critics will point out that Rust still is plenty complex, of course, and I think that's healthy skepticism too.
- gbersac 12y agoWhen I hear Stockholm syndrom, I always think javascript and css ^^
- JoshTriplett 12y agoThat was my reaction as well: not just the sigils, but in general Rust used to have a much larger language, and dropping the sigils was part of a shift towards having a much smaller language and larger library. That seems like a feature, not least of which because libraries can be improved and replaced.
- lambda 12y agoYep, the dropping of the sigils was a big help in my actually giving the language a chance. It's been on my radar for a while, but went through a pretty ugly period for a while before coming out much better than before. There was also just a sense of "OK, I get what these things do, but when should I us an @ vs an ~ vs a & in my API", and now I feel like it's much more clear what you use the different reference types for.
- tav 12y agoNo worries. All forgiven :) Thank you ever so much for the hard work done by yourself and the rest of the Rust developer community. It has been an absolute pleasure seeing the language evolve, and now that it's hit 1.0, I look forward to the incredible opportunities it makes possible. It takes great courage to go against the grain in terms of the core language (e.g. abandoning GC, M:N scheduling, etc. as core parts of the language), but the end result promises some truly exciting times. Thank you again and thank you also to you and the others for commenting here on HN despite the heavy criticism at times and being ever so helpful for those of us on IRC. It's been a fantastic ride and I look forward to it getting even better.
- steveklabnik 12y ago> It takes great courage to go against the grain in terms of the core language So, what I like to say is this: If you look at Rust by mission statement, it hasn't changed at all. If you look at it by feature list, it's a completely different beast. The focus of Rust has always been a safe, fast, concurrent systems language. It just took a while to figure out exactly how we wanted to accomplish that goal.
- madez 12y agoAnd I'm grateful that you took your time to let the language mature. If Rust fulfills it's mission statement, it might become widely adopted. While that's generally good, it also makes changes to the language hard, see C++. So, let's hope you got the things right that you can't change without breaking compatibility.
- derefr 12y agoCurious here: would Rust be a better language for writing the VM of an M:N-scheduled platform? Like, would rewriting Erlang's BEAM in Rust be a win?
- steveklabnik 12y agoSo, in general, Rust should be good for writing VMs. If you want a JIT, though, Rust may not have any super huge advantage with it, specifically, as it would basically be all unsafe anyway. There was a really great blog post about writing a Scheme implementation, including a GC: http://fitzgeraldnick.com/weblog/60/ http://fitzgeraldnick.com/weblog/60/
- bliti 12y agoLook at it this way: You beat Perl 6 to market. :)
- munificent 12y agoCongrats on 1.0! If you thought language design was hard before wait until you try to keep doing it without breaking anything. :)
- krelian 12y agoI think that if there is a place where people can sympathize and forgive you for over confident time estimates it must be on HN.
- frik 12y agoGreat, congratulations! Also let's mention Servo (browser engine) - the project has a symbiotic relationship with the Rust programming language, in which it is being developed (also from Mozilla). https://news.ycombinator.com/item?id=9541138 https://news.ycombinator.com/item?id=9541138 (two days ago on HN) and its website: https://github.com/servo/servo https://github.com/servo/servo
- ChuckMcM 12y agoIt is an excellent achievement, congratulations! For what its worth Java had an even longer gestation period and it wasn't until Eric Schmidt declared that we had to have 1.0 in Bert Sutherland's desk by 1/1/95 or "else" did it actually get to that point. I'm really excited to start trying it out in earnest. This is a bit disconcerting though: ls -lh total 588K -rwxrwxr-x 1 cmcmanis cmcmanis 8.4K May 15 13:02 hello_world -rw-rw-r-- 1 cmcmanis cmcmanis 83 May 15 13:02 hello_world.c -rwxrwxr-x 1 cmcmanis cmcmanis 565K May 15 13:01 main -rw-rw-r-- 1 cmcmanis cmcmanis 42 May 15 13:01 main.rs I'd love to write a safe embedded system in rust and that is going to mean much smaller footprint for a 'hello world' level of program :-)
- madez 12y agoAs you can already read in this thread (see [1]), this is due to static linking of the whole standard library. This limitation is known and solutions are being worked on. [1] https://news.ycombinator.com/item?id=9552468 https://news.ycombinator.com/item?id=9552468
- steveklabnik 12y agoOnly one component of the three is really even being worked on, the other two are there: use LTO or dynamically link. Not linking to the standard library itself is behind a feature gate for now, but it should be relatively easy to stabilize in the future.
- mwcampbell 12y agoIt might also help to have the option of using libc's malloc rather than jemalloc.
- steveklabnik 12y agoCustom allocators are certainly a thing that's coming in the future. :)
- ChuckMcM 12y ago
- deleted 12y ago[deleted]
- mlitchard 12y agoAll forgiven. This is great news.
- PopsiclePete 12y agoThanks for all your hard work on this amazing project. I am currently learning it and liking it a lot! If I could, make a little suggestion? Focus on building a community around the language, the way Go did, which was masterfully executed: Newsgroups, conferences, videos, tutorials, more videos, talks, speeches, more tutorials, books, articles, blogs, docs. All of that, churning non-stop. It's tedious. It's just as much effort as the language itself. I realize that. But it's truly why I even bothered with Go, which is, IMO, arguably a not-as-exciting language as Rust, yet already has amazing library/community involvement and support.
- Manishearth 12y agoBeing a project that Mozilla is invested in; I bet this is going to happen pretty well. Mozilla does community growth very well, and they care a lot about it. (Also: these things already happen to a degree, and I hope they start happening even more now that 1.0 is out!)
- jorgearturo 12y agoEven though a solid package manager was enough to get me on board, I deeply agree with you in that building a community around it will make all the difference. I'd also like to think it will be a bit less difficult for Mozilla to accomplish this because, well, Mozilla's values inspire loyalty, even love in my case, I love Mozilla.
- jwiley 12y agoThanks for your work on Rust, a very cool language. And although the massive 3k poem was removed Rust-created binaries, and it initially pissed me off when I discovered it, thanks to Brian Anderson for sharing. https://github.com/rust-lang/rust/issues/13871 https://github.com/rust-lang/rust/issues/13871
- eranation 12y agoAny plans to take Rust to the big data arena? Oh how I wish I had Spark Rust API... lower memory footprint, no GC, yet it will be pretty straight forward to migrate Scala / Python jobs to Rust (with a small memory management / borrowing concepts learning curve I assume).