More safe defaults also means I have to think more about escape hatches. Sometimes ignoring an error is the intended way of operation, although rare. Same goes for some other parts of the go coding standards. Sometimes you need to violate them and having to first use some escape hatch like Rust's unsafe is annoying.

I'd rather just keep track of linter complaints.

Yes, ignoring an exception is an explicit move when the default mechanism is to abort execution. Since it is rare, I don't see a problem.

> I'd rather just keep track of linter complaints.

Do you dislike "unused variables" being compilation errors, too?

Not really. It has changed my coding style so I now only add variables when needed, even in languages like JS. I only get the "unused variable" error about once a month.