It's a memory safety concept. In languages like C you allocate memory yourself, and then you have to make sure to free it up too. This is error prone. In garb

It's a memory safety concept. In languages like C you allocate memory yourself, and then you have to make sure to free it up too. This is error prone. In garbage collected languages like Java there is a garbage collector who figures out when is a piece of memory no longer in use. This has run-time cost. The third possible way is to make the ownership of that part of the memory explicit. This way the compiler can check memory safety at compile time. There is a much better description of this in the Rust book: https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html https://doc.rust-lang.org/book/ch04-01-what-is-ownership.htm...