The Go team's stance on generics has never been "generics = bad", but "generics have advantages and disadvantages, and if we find an implementation which finds a good compromise between the advantages and disadvantages, we will do it". Which they now did. Let's hope it really turns out to be a good compromise...

It remains to bee seen, meanwhile Rob Pike did comment[0], we should refrain from changing libraries in 1.18 immediately after generics are in.

"The reason is simple and compelling: It's too much to do all at once, and we might get it wrong."

[0]: https://github.com/golang/go/issues/48918