ohto

I'm at the point that I don't even try new Google products because I don't trust that they will stay around. I got burned too many times: Wave, Knol, Google Health, Buzz, Notebook, Answers, and most importantly Google Reader.

There is just no way I'm investing time in any new Google product. They are untrustworthy.

For instance, why on earth would I want to use Allo when still Hangouts exists? We know one or both will get cancelled within a year or two. I'm not going to sick my neck out and try to get my friends and family to use one of those platforms only for them to go away.

Nonsense. Reread the FAQ. They are choosing to not implement generics. If someone can find a way to implement them without violating Go's design principles, they will. In other words, it's a choice. It's not that they just haven't got around to it.

It is fairly clear by now that omitting generics is not an oversight, but rather a design choice. If you disagree, it sounds like Go isn't for you. Maybe it's time to just move on and ignore it instead of beating a dead horse.

I am always confused by the push to make every language exactly the same by using the same paradigms and features. Some languages try to take a different approach. If you can't figure out how to work within that paradigm, don't use it. Your comment is akin to complaining that Haskell doesn't support an imperative style.