When I read this kind of thing, it makes me so thankful for a bunch of #Rust features:
1. The Editions system
2. Macros allowing syntax changes to be libraries
3. A language that wasn't afraid to be complex at the start, so it didnt need to be complicated later  

https://www.theregister.com/2026/03/02/generic_methods_go/

Generic methods arrive in Golang, but they weren't the top dev demand

: Approved proposal reverses earlier stance, even as survey highlights bigger frustrations

The Register
@noboilerplate language design is difficult. It is one of those problems that, if you don’t get it right (enough) on the first attempt, then you are stuck with whatever failures you’ve now codified. Go got some things right and came up with some neat solutions, I’m glad it did so. Though, it also got a lot wrong in my opinion. In particular I find it really difficult to like the syntax. See the “Function Signatures” section of this post: https://kilo.bytesize.xyz/go
Go

My experience with Go began a few years ago in a brief attempt to see what the buzz was about. I had waded into the cloud native world ru...

kilo.bytesize
@noboilerplate Rust gets a *lot* of things right. Not only that, but Rust was far enough in the right direction to allow it to continue to improve without upsetting the underlying base. It still does get some things wrong and has problems that make me dislike using it, but the language really has cemented itself as one of the best.
@noboilerplate one thing I do respect is that they’re willing to change their minds, rather than doubling down on the original reasons for refusal.