News for hackers. Stuff that matters.
Re:Everyday hassles in Go by vardump on Tuesday December 30, 2014 @08:23AM (#8814459)
The big thing people miss is that while lack of generics might cost them effort worth X, other Go features benefits them Y. The value of Y is pretty large in case of Go, when it comes to concurrency and language level simplicity. It's hard to go wrong in Go.

Whoever designed Go seems to have some experience debugging and maintaining large concurrent systems.

When you design a language, you have to be so careful of things you add. Because otherwise you get C++ (or one of those cute let's-add-all-the-features-we-can-think-of scripting languages). In good and in bad. You can't remove features afterwards, so better not add a feature you can't get right from the beginning.

Re:Everyday hassles in Go by threeseed on Tuesday December 30, 2014 @03:22PM (#8816531)
Nobody is saying Go should rush to implement generics or any other feature.

The issue is more the dismissive attitude towards them.

Re:Everyday hassles in Go by davecheney on Wednesday December 31, 2014 @02:29AM (#8818534)
Citation needed please. Ian Lance Taylor, a core member of the Go team has revised and replied to many of the generics debates on go-nuts.