Rust 1.0: Scheduling the trains
I'm pretty stoked about this. I've been following Rust since 0.4, and it's been super fun to play around with. I have two major problems with it, but none of them are Rust's fault -- purely flaws of my own:<p>1) I have no idea what to do with it. I'm primarily a web developer, and I really want to get into systems programming, but I have no idea what to do with it or where to start. I wound up implementing about 50 different Rosetta Code things in Rust 0.9 and 0.10, but I still never came up with a really solid use-case that I could start and finish.<p>That said, I've been really impressed by rust-doom (<a href="https://github.com/cristicbz/rust-doom" rel="nofollow">https://github.com/cristicbz/rust-doom</a>) and the new Iota editor (<a href="https://github.com/gchp/iota" rel="nofollow">https://github.com/gchp/iota</a>), and I wish I had the know-how to even start down that path.<p>2) Given that the last time I touched systems programming was in college (15 years ago), I've found it difficult to wrap my head around some of the concepts (ownership in particular). I actually hung out in the IRC chat room for awhile, but I felt more than a few times that people were treating me like an idiot because of my questions ("Ha! You did X? Why in the world would you do that??"), so I wound up not really going back. I'm sure it was all my imagination and that I'm just being sensitive, but I think it would be very helpful to have more people interested in getting new people on board -- specifically people like me, with over a decade of programming experience in higher-level languages.<p>I guess the TLDR of this is: I love Rust, but I don't know what to do with it.<p>Congrats to the Rust team, though. 1.0 is a huge milestone. Good job!