this post was submitted on 07 Jun 2025
20 points (100.0% liked)
Golang
2495 readers
4 users here now
This is a community dedicated to the go programming language.
Useful Links:
Rules:
- Posts must be relevant to Go
- No NSFW content
- No hate speech, bigotry, etc
- Try to keep discussions on topic
- No spam of tools/companies/advertisements
- It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I liked the thorough explanation of the decision process, but I think universal approval is a paralysing requirement. This risks stagnation.
Especially when compared to generics. They spent so much time on that, and for what? They say themselves that most users are unlikely to use or encounter it. Personally, I've found Go generics to be useless in most of the cases they'd be handy, because of the limitation about methods being required to match struct specifiers. Everywhere else I've used them, I could have easily worked around them and probably come out with more clear code.
Error syntax jockied with generics for first place user concern for years, and they chose to roll out the change that would have a lesser impact on user convenience and code readability.
Bitter Ruaidhrigh is bitter.
They weren’t looking for universal approval. They were looking for widespread/majority approval.