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.<p>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. :)
For anyone that hasn't played around with rust yet, this is why I'm excited about rust: <a href="https://github.com/Azdle/hello-gtk.rs/blob/master/src/main.rs" rel="nofollow">https://github.com/Azdle/hello-gtk.rs/blob/master/src/main.r...</a><p>That is a GTK GUI application that makes HTTP requests in under 40 lines of code.<p>Don't get me wrong I love all the safety gaurentes and what not, but just being able to write quick simple apps that would usually be a pain to write in C is a game changer for me. A lot of this is down to Cargo (the Rust package manager, very npm-like imo) and all the great rust libraries that already exist. I'm super excited to see where this goes now that it's 1.0, people can stop worrying about breaking changes in the language and just get down to writing libraries to do everything.
Now that Rust reached v1.0, I may finally look into it without the fear of wasting time to learn stuff that will change within next months. (It's quite sad, though, that recently released Debian Jessie won't have it in its main repositories.)<p>Allow me to ask some questions, because I cannot easily find the answers and they're IMHO crucial for wider Rust adoption:<p>1. What CPU architectures/platforms Rust currently supports?<p>2. What's the state of cross-compilation support?<p>Most of devs have workstation on i386/amd64, but some of us may work with ARM, PowerPC and other architectures. Rust's memory safety seems appealing for embedded solutions, but can it be used there already?<p>BTW The install page is not well-thought-out.<p><a href="http://www.rust-lang.org/install.html" rel="nofollow">http://www.rust-lang.org/install.html</a><p>Unless I hover on the 32-bit/64-bit links and read addresses they point to, there's no way to tell whether it's for x86 or ARM for instance. And installation via piping script that is being downloaded to shell is something that shouldn't be present at all.
Thank you so much to all of our community and contributors. It's been a long time coming, but I'm really proud of what we've done together.<p>I'm finally going to get some real sleep tonight, I think.
This is so huge!<p>Rust is going to be the first time I am going to learn a programming language from the day it is born (until now it was tough to learn Rust, given the changing APIs ;).<p>I see a bright future for Rust. Thanks to Mozilla and the whole community for making it possible.
Congrats to the team and thanks for your hard work! I'm not a Rust developer but it's definitely piqued my interest in doing more native development without being afraid of introducing buffer overflows and other security exploits.
Awesome! I assume you intentionally released this on a Friday just to eat up everyone's weekends :) Thanks for the hard work. As I dig in, I'm hoping that Rust will fit in the "useful and safe" sweet spot in Simon Peyton Jones's diagram here: <a href="https://www.youtube.com/watch?v=iSmkqocn0oQ" rel="nofollow">https://www.youtube.com/watch?v=iSmkqocn0oQ</a>
If you haven't played with Rust yet and are looking for some puzzles to help motivate you to learn, we've updated our Bloomberg CodeCon[1] site to support Rust 1.0. You can login and click the "Challenger Series" to get 17 problems of varying difficulty to solve in Rust.<p>[1] <a href="http://codecon.bloomberg.com/" rel="nofollow">http://codecon.bloomberg.com/</a>
Well done! I'm generally against shoehorning languages into environments where they don't belong, but I can't wait to try using Rust for webdev.
Congrats! I've been excited about Rust for a while now, and this gives me a good reason to look into it a bit more. A quick question, though, if it's appropriate in this context:<p>It seems to me that the borrow checker disallows behavior that I (perhaps naively) wouldn't be concerned about. For example, if I have this C snippet:<p><pre><code> { // Safe C
int *ptr = NULL;
int val = 42;
ptr = &val;
}
</code></pre>
Everything is hunky-dory. Translating this to Rust results in this (I think):<p><pre><code> { // Malformed Rust
let ref: &i32;
let val = 42;
ref = &val;
}
</code></pre>
Now the borrow checker tells me that "val" doesn't live long enough, because the reference comes to life before the value. It seems like this should be safe behavior, because the reference isn't bound to the value until after the value comes to life.<p>Can anyone shed some light on this for me? I'm all for safety, but this in particular seems like something that I should be allowed to do.
It's always exciting reading Rust posts on HN, so very happy about a stable release!!<p>I can't help but feel the language has a very steep learning curve, however; doing something like making an event-queue-with-callbacks is very hard to write out in Rust if you're a beginner with just the current docs.<p>I think Rust will benefit greatly if their docs compiled some articles on how to write typical systems-related code (for me, I would love to see how to implement task queues with callback mechanisms).
I thought 1.0 was announced a few weeks ago. Am I going crazy? I mean it's awesome news I'm just confused.<p>Edit: looks like I'm going crazy. It seemed so vivid too like I actually started checking out the rust documentation and was looking for a book to pick up. Unless everyone is messing with me...
Thanks so much to everyone who contributed to this milestone. Rust is one of the few pieces of new technology that has made me want to drop everything and dig in to it.<p>It's also one of the few open source projects that has actually gotten me to contribute.
Is there anywhere I can download a Rust tutorial in kindle format? I'd like to start learning Rust this weekend.<p>EDIT: To answer my own question: <a href="http://killercup.github.io/trpl-ebook/" rel="nofollow">http://killercup.github.io/trpl-ebook/</a>
Great! I just downloaded and installed it, and my programs still worked!<p>No more "cargo clean; cargo update; cargo build; cargo test;" every day! At last.
Let me begin by saying congratulations to the Rust team and supporting community. I've been following Rust when I realized it would make for a good language to try with robotic controls (due to all the safety stuff). Stupid question time: What does this release mean for the embedded / control systems community? Will you be recommending any specific boards / micros / libraries from now forward? If so, which?
Very cool. Going to try to learn some basics this weekend! Exciting times watching (from a spectators points of view) the evolution of Rust to this point. Sounds like more exciting times ahead.
Congratulations to the team; it is nice to be around when a language is born. I remember when Ruby was born, and most people (that I knew) were like "Huh? Why Ruby, when we have Perl?".<p>I haven't followed Rust much, but as a total n00b: what are some <i>practical</i> reasons why one would choose to learn Rust? What features does this language have which others (pick: C, C++, D, etc.) don't have? What does it do better than the aforementioned languages? (Please don't take these as a challenge, but as a desire to learn more). Thanks!
I think the release of the first stable version is an appropriate time to ask how the collaboration with packaging teams from major distributions is going.<p>Can you give us some information on that?
Rust is nice, but… Why can't anybody made a language with the exact syntax of Python, but compiled? It doesn't need extreme safety features or other buzzwords.
I'm on a Late 2013 Retina MacBook Pro, running 10.10.3, with the latest stable toolchain. It would not compile.<p><a href="http://pastebin.com/bifK665u" rel="nofollow">http://pastebin.com/bifK665u</a><p>I set --prefix=/usr --enable-debug<p>No dice. I also tried to build from source in a VM on that same machine. 32-bit Ubuntu 14.04.2 (3GB of RAM), latest stable toolchain. Again, didn't compile. Core dump.
I was looking to see what UI and database bindings were available as crates and came across the crates.io web site.<p>It would be useful for people new to Rust to see what existing libraries are available and one way would be to have a link on the www.rust-lang.org site's font page pointing to crates.io site.
Very exciting! I've worked through the tutorial in the past and enjoyed Rust very much but since then have just been passively following progress on HN. Looking forward to actually building something with it now.