Go is still not good (blog.habets.se)

Article summary

The article discusses the author's criticisms of the Go programming language, including issues with error handling, nil values, portability, and memory management. The author argues that these problems were avoidable and that Go's design was not well thought out. The article also mentions the author's frustration with Go's limitations and how they have led to difficulties in writing and maintaining code. The author believes that Go's flaws are not just minor issues, but rather fundamental problems that make the language less useful than it could be.

Main themes

• Go language criticism
• Error handling
• Language design
• Portability
• Memory management
• Programming language comparison

What commenters say

• Go's simplicity and ease of use make it a good choice for certain tasks, such as API glue, despite its limitations.
• The language's design flaws, such as its error handling and nil values, are significant and frustrating for developers.
• Go's lack of features and type safety make it less desirable than other languages, such as Rust or Python, for certain use cases.
• The language's popularity and adoption are due in part to its backing by Google and its ease of use, rather than its technical merits.
• Go's standard library and tooling are robust and well-suited for certain tasks, but may not be sufficient for more complex or demanding projects.
• The language's limitations are not necessarily a problem for most business software, which often prioritizes ease of development over technical excellence.
• Go's design and limitations are a result of its origins and goals, and may not be suitable for all use cases or developers.
• The language's community and ecosystem are still evolving, and some developers are working to address its limitations and improve its usability.