Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
But that's not even my complaint about golang errors. As always with this language, the execution sucks. It's bizarre is that a language so focused on strong standards doesn't provide a sufficient error handling model in the stdlib. The community more or less decided on this 3rd party library https://github.com/pkg/errors, but the stdlib recently added it's own methods. Neither are sufficient. Some libraries use opaque errors, others make an interface, others panic() to represent the same error. Some use the old stdlib, some use the new stdlib, some use pkg/errors, some make their own implementation. Every library is doing errors differently and it's a total mess.
Go also doesn't scale on a large codebase. you end up using hacks like source generation (https://github.com/kubernetes/gengo) and static analysis to make up for the shortcomings of the language. The jvm or .net have better tools for dealing with complexity imo. Jvm langs can compile to bin with graal.