Why I Decided to Learn Rust
I’ve been curious about Rust for quite a while. In late 2017, Mozilla released Firefox Quantum, an update to the browser that was about twice as fast as the previous version. I was curious to know what had changed. Turns out, Mozilla had incorporated a large portion of their experimental Servo engine into Firefox. Servo is written in Rust and is designed to take advantage of Rust’s memory safety and concurrency features. Servo also uses GPU acceleration to render web pages.
My interest in Rust only grew when I found out last year that Rust has been the most loved programming language, 5 years running, according to the Annual Stack Overflow Developer Survey.
Rust also compiles to WebAssembly, so I can still build applications for the web (which I love doing). WebAssembly is already paving the way for the next generation of web applications. Figma uses it for their multiplayer server, Dropbox uses Rust for optimizing it’s file storage. There are many more companies using Rust in production.
What I’m Doing Differently This Time
I’m taking a different approach to learning Rust. After getting the basics down, I’m diving straight into building breakable toys. I believe solving my own problems using something I’m learning is the best way to get better at it. I’ve a few ideas that will be perfect for Rust. Since Rust is usually called a systems programming language, some of what I learn will be around this area. I’m excited to learn about that as well.
I usually write about web development here, so I hope you don’t mind me writing about systems programming, Rust and whatever I build with Rust.