Member-only story
I Compared Goose and Rust’s Memory Models So You Don’t Have to Guess
Memory safety is only the beginning. The real question is which responsibilities the language takes off your plate, and which ones it hands back to you.
Imagine your game frees an enemy slot. A moment later, a new enemy is created in that same slot. An old reference you forgot about now points at the new enemy. Your program is still memory safe, but your game might attack the wrong target.
In Goose, this is allowed on purpose. If your mental model comes from Rust, that probably sounds wrong. But it points at the question I think matters more than “which language is better”: what becomes easier in Goose, and what moves into your own code?
How Goose thinks about memory
Goose builds its memory model around compiler-managed data stacks. These are separate from the normal function call stack. Dynamic data grows by moving a pointer forward, and when the scope that owns the data ends, its storage becomes reusable.
The compiler works out lifetime relationships for you, so a reference can never outlive the storage it depends on. You don’t write lifetime annotations. But you still decide where your data lives, and that…
