The stdlib I actually find quite complete. Especially for http projects. You really don’t need third party libs for that for example.
The errors were super strange to me at the start, but I’ve come to really like it over exceptions. It is similar to old error codes, but I feel that this makes one always have to be mindful of error handling and the non happy path (thinking of large Python projects where no one cares about exceptions).
A lot of people tend to compare Go and Rust, but I feel that the languages are just too different. Rust is good for a variety of things which don’t overlap with the things Go is good for.
The stdlib I actually find quite complete. Especially for http projects. You really don’t need third party libs for that for example.
The errors were super strange to me at the start, but I’ve come to really like it over exceptions. It is similar to old error codes, but I feel that this makes one always have to be mindful of error handling and the non happy path (thinking of large Python projects where no one cares about exceptions).
A lot of people tend to compare Go and Rust, but I feel that the languages are just too different. Rust is good for a variety of things which don’t overlap with the things Go is good for.
Technically you need a separate linter (
errcheck) to ensure you don’t just ignore errors. This is…not great. (That should have been a compiler error.)Yes, true. Having it built in in the compilation would be nice. Or at least having errcheck as a tool which already comes packed with Go.
Go has changed over time to include more things like this. Maybe one day this will be addressed.
Yeah, I was particularly glad to see the change in loop variable semantics become a stable part of the language. That was a terrible footgun.
There are other things I dislike about Go, but I do think it’s improving while maintaining its better qualities, which is no small feat.