It does matter, but if you have a problem with a tool you need to make an informed statement about it. Instead of yelling "Go needs generics!", look up the original reasoning behind the lack of them first - because they DID think about it, long and hard. (as an example)
> Instead of yelling "Go needs generics!", look up the original reasoning behind the lack of them first - because they DID think about it, long and hard. (as an example)
A lot of the people complaining about Go lacking generics knew about this and were just saying that the Go designers' conclusion was wrong, based on existing evidence: the myriad languages supporting generics without major issues.
If conservative languages such as Java and C# could get generics in 2005, surely Go could have gotten them as well, back in 2012.
