Go programming language is known to be easy to use. Thanks to its well-thought syntax, features and tooling, Go allows writing easy-to-read and maintain programs of arbitrary complexity (see this…

ITNEXT is a platform for IT professionals, developers, and technology enthusiasts, offering articles, tutorials, and insights on a wide range of topics, including software development, cloud computing, and machine learning. With a focus on practical solutions and real-world applications, ITNEXT provides actionable advice and best practices for navigating the complexities of modern technology landscapes. Developers can learn about  technologies, explore hands-on tutorials, and stay up-to-date on the latest industry trends through ITNEXT's engaging and informative content.

ITNEXT

The post discusses the criticism that Go programming language is facing for lacking advanced features from other languages. It highlights the negative impact of adding generics and the 'range over func' feature in recent Go releases, emphasizing the increased complexity and lack of clarity in code. The author suggests focusing on essential Go features like simplicity, productivity, and performance to compete with languages like Rust.

Go evolves in the wrong direction

I used generics recently when I built my own Dependency Injection system. It was great for type-safety but the p99 of go code I do doesn’t require generics.

TBH, even tho we now have generics, I haven’t used it in real code so far. Range over func on the other hand seems a nice addition that I hope to use soon.

I personally hate having more than 1 way to do something. I get why someone would want methods like <code>.filter</code> in any language, but I hate how it opens space to terrible code optimization and the necessity of linters to ban it.
It’s very sad to see Golang going this way.

I agree with the posts point of view about simplicity. But i still think generics and generators are warmly welcome in my world since they do have a use case.

Second time in 10 minutes when I see a post about GO evolving in the wrong direction.
Now I remember seeing titles like this about React, TypeScript.
Wrong direction, quite a vague term.