One day, after a particularly arduous coding session with Rust, I decided to vent my frustrations with this language on pen and paper (or keyboard and pixel?). My rant ended up going viral.
I spent 18

Denis Bolkovskis

Mental Health

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The author shares their experience of rebuilding their algorithmic trading platform in Rust after initially facing significant challenges. Although Rust's steep learning curve was frustrating compared to languages like TypeScript and Go, the author ultimately appreciates Rust for its speed, maintainability, and unique features. The platform's performance improved significantly, and the author provides tips for mastering Rust.

I spent 2 years rebuilding my algorithmic trading platform in Rust. I have no regrets.

Why did I choose Rust in the first place?

<p>I try to not use clone when I can use reference, but you’re right. It’s so harder to write good code without clone when it is the first language that you have to handle references (I’ve only do java, .net, typescript, … - non C or go).
But I think if you have to get the most perf has possible, it may be an amelioration area</p>


<p>I try to lean more on refs instead of clone, but there are obvious tradeoffs.  Especially when you are first learning.  In my tests though I use clone all over the place since perf in test usually aren’t a high priority for me.</p>
