(blog.habets.se)

644 points ustad | 5 comments | 22 Aug 25 09:25 UTC | HN request time: 0.735s | source

1. tapirl ◴[22 Aug 25 15:43 UTC] No.44985971[source]▶

Go indeed has its problems. But the ones described in this article just prove the author is a Go newbie.

2. laserlight ◴[22 Aug 25 16:48 UTC] No.44986737[source]▶

In a comment in this thread, the author states that they have 12 - 15 years of experience in Go [0].

replies(1): >>44986830 #

3. tapirl ◴[22 Aug 25 16:55 UTC] No.44986830[source]▶

but still a Go newbie?

The article's points feel overly simplistic/shallow and lack the depth you'd expect from an experienced Go programmer.

4. thomashabets2 ◴[22 Aug 25 20:33 UTC] No.44989487[source]▶

I won't be dumping credentials, but perhaps the newbie is you?

I also review a lot of Go code. I see these problems all the time from other people.

replies(1): >>45007352 #

5. rustandmore ◴[24 Aug 25 20:11 UTC] No.45007352[source]▶

Most of non-opinion parts of this article are "Go sucks because <insert newbie mistake>" or otherwise factually incorrect points.

At that point, all languages suck because there's newbie mistakes and I don't understand them.

Maybe it is time to dump credentials rather than being obscure. I don't believe it for a moment that you have decade+ experience in Go.

Go is still not good