A Rust journey: from Haskell to Rust as the first-choice language
This series offers a look at the perspectives and experiences of the Rust community leaders who are shaping this lively ecosystem.
Welcome to our Rust interview series!
With Rust turning 10 in 2025, there’s no better moment to celebrate the language and the thriving community around it. This series offers a look at the perspectives and experiences of the Rust community leaders who are shaping this lively ecosystem.
Our first guest is a software developer and blockchain specialist at a functional programming consultancy who heads a team of developers passionate about Rust and functional programming. His expertise spans strongly typed programming, actuarial science and economics, including blockchain development, statistics and software architecture.
How did you first get introduced to Rust, and what were your initial thoughts about it?
For more than ten years, I’ve been convinced that strong typing is the basis for building better software. Several friends from the Haskell community kept telling me about Rust and singing the praises of what it could do. My first reaction was, “It’s an excellent substitute for C++, but I’d rather not handle memory management manually in my application code.”
Can you share a moment when you realized, “Wow, Rust is amazing”? What features or capabilities of Rust made you feel that way?
Here are the Rust features I liked best when I first looked at it:
- strong types,
- sum types,
- pattern matching,
- memory safety,
- traits,
- and iterators.
In essence, they were all the things I loved in other languages, smoothly combined into a coherent ecosystem with excellent tooling. No persuasion was necessary.
Back when I started with Rust, it still had plenty of rough edges. Thanks to the continuous work on its ergonomics, though, those problems have been eliminated to a sufficient degree. After the pain points were addressed, Rust became the language I reach for first.
What’s your favorite programming meme?
I’m not sure it’s my favourite of all time, but this one always gets a chuckle out of me:
Source
Or simply a joke:
Computer science has 2 hard problems: naming things, cache invalidation, and off-by-one errors.
What advice would you give to someone just starting out with Rust?
Call clone freely and don’t overthink it. It’s easy to get caught trying to over-optimize every bit of your code, steering clear of unneeded memory allocations or even reference counting. That’s a fine long-term aim (and Rust makes it remarkably attainable), but it isn’t where you have to begin.
As a Rust beginner, lean on the language’s safety features, accept some performance trade-offs in order to get things done, and concentrate on growing your confidence. With time, as Rust becomes more familiar, you’ll naturally begin noticing chances to tune your code for better performance.
And: use clippy and take its warnings seriously. You’ll learn a great deal.
How have you seen Rust evolve over the years, particularly in your area of work?
The biggest change by far is async/await. I wrote an introductory series of Rust blog posts, and part 7 dealt with using tokio before the language had async/await. The difficulty was off the scale – it was easily the toughest blog post I’ve ever written. Once async/await arrived, a huge number of complicated topics just disappeared.
What do you predict for the future of Rust over the next decade?
Gradual improvements to the language, nothing revolutionary. More real-world adoption. I think a new generation of programmers will start entering the market who see Rust not as a trendy new technology, but as the standard way of writing high-quality code.
Is Rust only for systems programming, or do you see it as a valuable technology in other areas as well?
What surprised me most about Rust is how well chosen its design trade-offs are. Even without the conveniences of a garbage collector, its other strengths make it a great fit for a broad range of applications. That covers server-side programming (where I spend most of my time), smart contract development, frontend coding, mobile apps and a lot more.