I Want Off Mr. Golang's Wild Ride (fasterthanli.me)

Article summary

The article discusses the author's frustration with the Go programming language, specifically its handling of file systems and metadata on non-Unix platforms like Windows. The author argues that Go's simplicity comes at the cost of complexity being swept under the rug, leading to issues when dealing with edge cases. The article compares Go's standard library to Rust's, highlighting the latter's more robust and type-safe approach to file system interactions. The author concludes that Go's design decisions prioritize simplicity over correctness, leading to problems in certain use cases.

Main themes

• Go language limitations
• File system interactions
• Simplicity vs correctness
• Cross-platform support
• Language design trade-offs
• Rust comparison

What commenters say

• Some commenters argue that Go's limitations on Windows are not a significant con, as the language was designed with Unix in mind and Windows is a secondary platform.
• Others disagree, stating that a language should strive for correctness and robustness across all platforms, not just prioritize simplicity for the majority case.
• A few commenters suggest that the article's criticisms are minor and do not warrant abandoning the language, while others share similar frustrations with Go's design choices.
• Some argue that Go's simplicity is a trade-off for ease of use and development speed, and that the language's goals do not include being a perfect fit for all use cases.
• The article's comparison to Rust is seen as unfair by some, who argue that Rust's more complex approach may not be necessary or desirable for all projects.
• Others appreciate the comparison, highlighting the importance of robust and type-safe libraries in preventing common errors and edge cases.
• A few commenters note that the article's tone is overly negative and dismissive, while others find the criticisms valid and relevant to their own experiences with Go.