Programming languages are usually divided into two camps: Manual memory management like C or C++, or managed memory via garbage collection (basically every other popular programming language) -- but what if there's another way?

Rust defines all memory movements at compile time, and its unique ownership model guides developers through potentially troublesome scenarios. The result? 100% memory safety, no extra overhead. But is it as good as it sounds? Or does it come with an entirely different set of trade-offs?

In this talk, we will explore Rust's ownership model and talk about memory management in detail.