My journey from C/C++ to the beauty of Rust Ownership
โ Rust ๐ 2026-05-01 ๐ค surdeus ๐๏ธ 3Hi everyone,
Iโm Youness, a software developer currently studying at 1337 UM6P (42 Network) and Zone01 Oujda. Coming from a background heavily focused on low-level systems programming in C and C++, I recently completed an intensive Rust Piscine.
After years of manually managing memory and debugging segfaults in C, diving into Rust was a revelation. I wanted to share my perspective on why I believe Ownership is one of the best ideas in modern programming.
Why Ownership is a Game Changer:
- No More Manual
free(): In C, the mental overhead of tracking every allocation is exhausting. Rustโs ownership rules (specifically the concept of "Scope") handle this automatically without the performance hit of a Garbage Collector. - The "Borrow Checker" is a Mentor, not an Enemy: At first, I fought the compiler. But I realized that the borrow checker is effectively a real-time code reviewer that prevents data races and "use-after-free" bugs before the code even runs.
- Safe Concurrency: Moving from C to Rust, the way ownership handles threads is incredible. By ensuring that only one writer (or multiple readers) can access data at a time, Rust makes "Fearless Concurrency" a reality rather than a marketing slogan.
- Memory Safety by Design: In the 42 Network curriculum, we learn to respect memory. Rust turns that respect into a set of strict, logical rules that guarantee safety without sacrificing the "close-to-the-metal" performance I love about C.
I am currently working on integrating Rust into my full-stack workflow and exploring its potential for systems projects like my Minishell or algorithmic challenges like Lem-in.
Iโm excited to be part of this community and look forward to learning more from all of you!
Happy coding,
Youness Laidi
1 post - 1 participant
๐ท๏ธ Rust_feed