News for hackers. Stuff that matters.
Re:Why Go Is Not Good (2014) by gohrt on Wednesday December 09, 2015 @11:17AM (#10704517)
Then good that it stopped years ago:

https://golang.org/doc/

>>> The Go programming language is an open source project to make programmers more productive.

Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. <<<

Re:Why Go Is Not Good (2014) by stcredzero on Wednesday December 09, 2015 @01:01PM (#10705416)
Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines

But more realistically, it makes it easier. Those things still manage to be hard at some point.

Re:Why Go Is Not Good (2014) by iofj on Wednesday December 09, 2015 @12:55PM (#10705347)
"expressive"

"concise"

"novel type system"

"flexible type system"

Just a few things that need correcting. Really ... "novel type system" ...

Re:Why Go Is Not Good (2014) by adrusi on Wednesday December 09, 2015 @01:04PM (#10705456)
Ok, well that's funny. You pick "novel type system" apparently because you find it especially absurd, but I find that that's the only accurate on on the list.

Go isn't expressive, nor concise, nor does it have a flexible type system. But if any of its claims are true, it's that its type system is at least a little novel.

Sure it's not the most exotic type system out there, but its interfaces are very useful and they aren't found in many other languages (not implicitly satisfied interfaces, that is).

Re:Why Go Is Not Good (2014) by iofj on Wednesday December 09, 2015 @01:15PM (#10705563)
Go's brand of duck typing isn't exactly a novel type system.

If I had to describe Go, I'd say "I like Hoare's paper" combined with "I read the first 10 pages of the book 'my first compiler'".

Re:Why Go Is Not Good (2014) by incepted on Wednesday December 09, 2015 @05:08PM (#10707132)
> But if any of its claims are true, it's that its type system is at least a little novel.

Are you saying it's novel because it picked the worst features of past type systems? ;-)

Technically, it is indeed novel, but it's novel because making these choices was pretty dumb in the first place so nobody made them...