zlacker

[parent] [thread] 4 comments
1. tapirl+(OP)[view] [source] 2025-08-22 15:43:36
Go indeed has its problems. But the ones described in this article just prove the author is a Go newbie.
replies(2): >>laserl+mc >>thomas+IU
2. laserl+mc[view] [source] 2025-08-22 16:48:09
>>tapirl+(OP)
In a comment in this thread, the author states that they have 12 - 15 years of experience in Go [0].

[0] >>44985378

replies(1): >>tapirl+Rd
◧◩
3. tapirl+Rd[view] [source] [discussion] 2025-08-22 16:55:12
>>laserl+mc
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. thomas+IU[view] [source] 2025-08-22 20:33:24
>>tapirl+(OP)
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): >>rustan+Ry5
◧◩
5. rustan+Ry5[view] [source] [discussion] 2025-08-24 20:11:47
>>thomas+IU
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 to top]