Live data from Hacker News

Why Go Is Not Good

yager.io

1–10 of 23 posts

Re: Why Go Is Not Good

#3
I get what you are saying, and that's why I am personally sticking with C++, and in the future Rust, but I can understand why many like the comfort of a simple language like Go. It has attracted many C developers who don't like the heavy abstractions that C++ and Rust offers.

Re: Why Go Is Not Good

#4
User defined operators frequently lead to programs that are difficult to understand, e.g. what is this '+'. When reading you will probably at first assume that it is adding two numbers, but then you also have to consider all other versions of this operator function. A function call with a good descriptive name is much clearer.

Re: Why Go Is Not Good

#8
Go seems to be a favorite language to hate, and yet, there's a lot of awesome software in the world because of it. It's simply and lack of features was intentional; not a design flaw. It was built by some of the premier computer scientists of our age not for lacking of knowledge of modern language features but intentionally avoiding complexity.

Choose Rust and C++ for building your next OS, but Go is great when I need to build a web service that's fast enough and hire a team that may not know the language walking in the door but can be productive quickly.

Re: Why Go Is Not Good

#9
> Generic Programming

The author does not seem to be aware that generics are coming in Go 1.18.

> Language Extensibility

Go was carefully designed to disallow this kind of extensibility. The point is that operators and other language constructs like `for ... range` always can be trusted and have a known cost. The author basically lists a pro as a con.

Post reply on HN