Day 24 - conclusion
So, 24 days have passed since the first article in the series. This means, sadly, 24 days of Rust is coming to an end. I hope you learned something from my articles or at least found something interesting about Rust to dive in. For me it was a great experience too, I learned a ton while doing this. Sometimes it was stressful too - breaking changes coming to rustc on a daily basis meant a considerable amount of work! A few times I had an already drafted article on some subject, only to discover the code blows up with the newest nightly and I have to change the topic. So here I go looking for something that works on that day, or fixing dependencies of dependencies just to make the examples compile. But no more complaining - there's something very positive I wanted to say today.
Thanks!
And that positive thing is a huge THANK YOU to everybody who read my articles, commented or critiqued. Your feedback is invaluable and it helped me get motivated to write more. Doesn't matter if it was in person or on Twitter, Reddit, Hacker News - thanks, you're awesome! Rusty Holidays to all of you!
24 days of Rust 2014 - archive
See the sidebar for a complete set of links for the series.
For a historical perspective you can take a look at the articles as they were originally written on my blog (note: these are pretty much outdated as of now):
- Day 1 - Cargo and crates.io
- Day 2 - slow_primes
- Day 3 - csv
- Day 4 - docopt
- Day 5 - hyper
- Day 6 - working with JSON
- Day 7 - itertools
- Day 8 - racer
- Day 9 - anymap
- Day 10 - the glorious tau
- Day 11 - postgres
- Day 12 - image
- Day 13 - uuid
- Day 14 - nalgebra
- Day 15 - FUSE filesystems, part 1
- Day 16 - FUSE filesystems, part 2
- Day 17 - from_fn
- Day 18 - redis
- Day 19 - rusti
- Day 20 - zeromq
- Day 21 - rust-crypto
- Day 22 - built with Rust
- Day 23 - calling Rust from other languages
- Day 24 - conclusion
Where to go from here?
I'm hoping to write more about Rust, so stay tuned. Meanwhile there are a few other resources worth checking out: