Teiva Harsanyi
1 min readAug 7, 2023

--

> How is this due to my lack of knowledge?

Because there are multiple ways achieving WHAT you want to do, not HOW you want to do it.

It's similar to the XY problem (https://xyproblem.info/) but in a different context: if you want to achieve X using Y, it's not because Y isn't possible that it makes the language bad; it comes from the fact that you didn't know how to really achieve X.

I recommend you read https://go.dev/doc/faq => _Why does Go not have feature X?_. Perhaps you will understand one of the core philosophies behind the language. You may like it or dislike it; of course, this is your opinion.

> What would be the Go approach to solve this?

I would have been glad to help you, but clearly not in this context.

> But it drew attention which is good :D

No, it's not good. You can bring something to the table without stating that a language is "bad" or that because something is missing it is "ridiculous"; this is clearly the wrong approach.

--

--

Teiva Harsanyi
Teiva Harsanyi

Written by Teiva Harsanyi

Software Engineer @Google | The Coder Cafe newsletter (https://thecoder.cafe) | 📖 100 Go Mistakes author | 改善

Responses (1)