Why I Program in Go

Re:Why I Program in Go by CJefferson on Sunday January 06, 2013 @06:53AM (#5016086)

Really? I remember reading all kinds of problems when trying to run go on 32-bit machines, like: http://news.ycombinator.com/item?id=3805302

[ Parent | on HN ]

Re:Why I Program in Go by enneff on Sunday January 06, 2013 @04:10PM (#5017749)

The 32-bit GC issue is an unfortunate shortcoming of the GC implementation, which will be resolved in Go 1.1 early this year. The issue was merely an artifact of dead simple conservative GC implementation.

OTOH, the memory model of the JVM is intractably linked with its design. Software that runs on the JVM must generate garbage, and so the JVM must include a highly sophisticated GC.

Remember how appallingly bad the JVM was when it was just a few years old? It didn't come close to where we are with Go today. We have only scratched the surface with GC (and other optimizations) for Go.

[ Parent | on HN ]

Re:Why I Program in Go by codygman on Sunday January 06, 2013 @07:10AM (#5016113)

You are correct, but the none of those problems happened on 64 bit machines which I find to be more prevalent these days.

[ Parent | on HN ]

Re:Why I Program in Go by CJefferson on Sunday January 06, 2013 @10:43AM (#5016560)

Still, this story seems much more crazy than any other gc issue I have ever heard of with the jvm.

[ Parent | on HN ]