>and makes you memorize when to use stack vs heap You don't have to think about stack vs. heap allocation in Go unless you're writing performance sensitive cod

>and makes you memorize when to use stack vs heap You don't have to think about stack vs. heap allocation in Go unless you're writing performance sensitive code. You could pretend that Go heap allocates everything and still read and write Go code without any problems.