🦀 I’ve spent the last few months exploring Rust after years working with high-level languages like Java. I’d always heard about Rust’s steep learning curve due to ownership and the borrow checker… but I wanted to see it for myself.
Spoiler: it’s not that scary. In fact, it’s been a great experience, and I wrote a post sharing my thoughts on tooling, performance, DDD, compile-time safety, and more.
👉 English version: <a href="https://dev.to/guuri11/rust-is-not-so-complicated-after-all-22g3" target="_blank" rel="noopener nofollow">https://dev.to/guuri11/rust-is-not-so-complicated-after-all-22g3</a>
👉Spanish version: <a href="https://dev.to/guuri11/rust-no-es-tan-complicado-despues-de-todo-2043" target="_blank" rel="noopener nofollow">https://dev.to/guuri11/rust-no-es-tan-complicado-despues-de-todo-2043</a>
Let me know what do you think

Welcome to the Rust Developers Community, founded by Francesco Ciulla, a passionate Rust Developer who loves making videos about this cool language.

Join us to learn Rust, share knowledge, and connect with fellow Rustaceans 🦀

Rust Developers

After exploring Rust, the author finds that despite its reputation, Rust's learning curve is not as steep as anticipated. The post shares insights on tooling, performance, domain-driven design, and the benefits of compile-time safety.

Rust is not so complicated after all....

it gets difficult when I stop using clone everywhere, and when async and streaming is involved

<a href="https://www.rustfinity.com/practice/rust/challenges/declaring-variables/description" target="_blank" rel="noopener nofollow">https://www.rustfinity.com/practice/rust/challenges/declaring-variables/description</a>