My Thoughts on Rust
I have been interested in Rust for about a year, in January 2017 I went through to about chapter 4 of The Book. I found Rust very enjoyable, different in its compiled-ness, attractive in its toolchain and stunningly fast to run. I described rust to a coworker.
If Python is like a Toyota Corolla, Rust is like a Tesla.
The more I think about both Python and Rust, the more I find that statement fitting.
|Common Teen or College Car||Common first language or learned in college||Rare for first car||Rare for first language, not taught at university|
|44.1 million sold||Number 2 by volume on github||236k sold||Ranked 18th on github|
|Base model is not fast||Vanilla Python not fast||Performance baked into the design||Designed for Speed|
|Steady Evolution of Design||Few breaking changes||Made by hand, few identical vehicles||Many core libraries still in pre 1.0 state|
|Your grandmother drove one in college (1966)||Python 1.0 - 1994||Founded 2003||Rust 1.0 - 2015|
In light of all this, Rust is just hard to learn. I don’t want to have to think about thread safety and ownership and memory usage. I just want to write some code and get work done. It is rare that a difference of 3ms vs 3 hours in run time makes a difference for me, what does make a difference is 15 minutes vs 5 hours to code it. After a few toy programs, I lost interest.
I still follow the Rust community. When they started their push to lower the bar to learning Rust I became intrigued again. With their successful push of so many core libraries to 1.0 in December 2017, I thought I would try again.
For some reason, it is still not sticking for me. I get to the part where The Book starts to explain ownership and suddenly I lose interest. There are some books scheduled to publish this spring. I’ll pick one up to see if that helps. Otherwise, I may try go-lang.
For now, I will stick with Python where I can get some work done.
The day after I wrote this post, I read Why is Rust Difficult? by Micheal Vaner. He perfectly outlines where I struggle with Rust and brings me to another question. Is there an eloquent explanation of Ownerships, Traits and Lifetimes? Preferably with pseudo code or IRL analogies instead of Rust. If so please send it to me in a tweet.
Please note that I am a huge Python fan, nearly an evangelist. I am active in my local Python community and it is my language of choice for just about everything.