[OT] Go officially won't get generics

[brad clawsie via Digitalmars-d]

On Friday, 9 May 2014 at 19:07:24 UTC, Jesse Phillips wrote:

> No, the context around what he said is very important. Google 
> isn't leaving Go development, generics are not nixed for Go 
> 2.0, the language will continue to see bug fixes. This is all 
> very clear with context.

I see this as a good. What would you rather use - a third party 
library written against abstractions or one written against 
concrete types? I would rather use a library based on concrete 
types. My observation is that the more abstraction people 
indulge, the greater the chance I will regard one of their 
abstractions as a code smell.

And it isn't the the case that the lack of generics is inhibiting 
participation. Go's library selection is already very good and 
getting better daily. Just yesterday I needed a Go lz4 
compression library and was able to find three distinct 
implementations. Go is not hurting for third-party libraries.