Our great sponsors
-
I disagree with at least half of your post, tooling in Go is amazing overall and there is one linter that pretty much every one is using: https://github.com/golangci/golangci-lint
-
The specific problem I'm talking about are how interface methods may not be generic, because there is no way to know which instantiation to call when working with an interface instead of a concrete type, see https://github.com/golang/go/issues/49085
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
eris
Error handling library with readable stack traces and flexible formatting support 🎆 (by rotisserie)
Attaching stacktraces to errors is one way to make errors more readable. Go has notoriously unreadable errors and when you log the error, the logging function is now at the top of the stack rather than where the error actually originated. There needs to be a simple function that adds some default wrapping when you return an error because as it is, you need packages like Eris to make the errors even halfway readable
