> if the code goes boom, it's on the developer
This is the same argument C (and Zig!) people have for manual memory management. You can avoid memory problems by being a good developer.
This is the same argument C (and Zig!) people have for manual memory management. You can avoid memory problems by being a good developer.
On the other hand, Go explicitly warns and tries to prevent you from ignoring or not handling possible errors. This is a bit different than a happy C compiler which doesn't warn you about leaking memory.