Why Go Is Not Good
yager.io
Why Go Is Not Good
1–10 of 23 posts
Re: Why Go Is Not Good
#2Re: Why Go Is Not Good
#3Re: Why Go Is Not Good
#4Re: Why Go Is Not Good
#5Re: Why Go Is Not Good
#6Person A: “go lacks feature X!”
Person B: “that’s what makes it so simple!”
And round and round it goes...
Re: Why Go Is Not Good
#7Flagged, here's some previous discussion: https://news.ycombinator.com/from?site=yager.io
Re: Why Go Is Not Good
#8Choose 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
#9The 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.
Re: Why Go Is Not Good
#10Compare https://github.com/ksimka/go-is-not-good