> More languages are incorporating them exactly because of how useful they are
No, more languages are incorporating them, because most languages operate under the assumption that "more-is-better" is a good design maxime, also known as the "everything-and-the-kitchen-sink" method.
Resulting in exactly the opposite of what Go is, with extreme success, doing.
Fun fact: That methodology in other langages is what made Go's success possible in the first place.
> I expect much like generics, we'll get some new version of Go eventually
I expect the exact opposite, precisely because of generics. Because it has been some time now since they were implemented, and lo and behold: They are rarely used in most codebases, because as it turns out, the people saying "Outside of some collection-types, generics are almost never required" were right in the first place.