News for hackers. Stuff that matters.
Re:Open Sourcing Our Go Libraries (2014) by beagle3 on Tuesday January 06, 2015 @11:58AM (#8845390)
Would that be over Java the Language? Java the Virtual Machine? Java the Ecosystem (Libraries, alternative languages)?

Java the Language:

1. Go is more concise. You might not care, but I do.

2. Go uses explicit error return codes.

My experience is that practically and counter intuitively, explicit error return codes (that have to be explicitly checked for errors) result in more robust code than exceptions (checked or not). YMMV.

Java the Virtual Machine:

1. Go produces single file native binaries. You may not care, but if you do, that's a win.

Java the Ecosystem:

1. Go interfaces to C more easily;

2. Go has a more vibrant, more enthusiastic community right now.

3. Go advances more quickly.

(Of course, I can think of a lot more reasons that the Java ecosystem wins - but you asked to sell you on Go...)

But if you're looking for a new language, rather then Go specifically, I urge you to have a look at Nim (nee Nimrod). It's very impressive. I think it's what Go wanted to be.

Re:Open Sourcing Our Go Libraries (2014) by pstuart on Tuesday January 06, 2015 @12:14PM (#8845481)
> 2. Go uses explicit error return codes

Small nitpick, but the default error value returned is a string.

Re:Open Sourcing Our Go Libraries (2014) by 2mur on Tuesday January 06, 2015 @12:46PM (#8845743)
Even more nitpicky, it is an interface. It is where you get into problems with nil interfaces and not returning an explicit nil value for the error.
Re:Open Sourcing Our Go Libraries (2014) by pjmlp on Tuesday January 06, 2015 @12:49PM (#8845772)
>Java the Virtual Machine:

> 1. Go produces single file native binaries. You may not care, but if you do, that's a win.

So does Java. It is only a matter of picking the right implementation.

There are certified implementations with AOT compilers.