News for hackers. Stuff that matters.
Re:Playing with Go1.1beta2, it's much faster by ghshephard on Tuesday April 09, 2013 @12:57AM (#5516506)
On HN there is usually a pretty high bar for making comments regarding performance, stability, etc...

I'm actually interested in what you have to share regarding performance characteristics of Go versus Java - but a bit more detail than, "Go has a some way to go still and it can be improved in all areas: GC, algorithms, heuristics, code generation," would be useful, particularly in comparison to Java, which you have called out.

Also - I think 36% is a pretty amazing improvement - particularly if Google can persist these performance increases.

Re:Playing with Go1.1beta2, it's much faster by trailfox on Tuesday April 09, 2013 @02:56AM (#5516800)
I agree that his comment need to provide more data. I also find that HN in general is very quick to downvote comments critical of Go, even well reasoned ones with sources.

In terms of performance data check out quad core results for Go 1 (go 1.1 would need to improve by considerably more than 33% to best the JVM):

http://benchmarksgame.alioth.debian.org/u32q/benchmark.php?t...

Also see Netty (Java) outperforming go by a wide margin here: http://www.techempower.com/blog/2013/03/28/framework-benchma...

The poster's comments regarding GC, heuristics and code generation are vague, but it's no secret that IBM/Sunoracle and co. have very sophisticated GC and JIT implementations which they have been optimizing for 15+ years and it shows through in the benchmark results.

I like Go, I just think that we need to be wary of expecting it to be as fast as the JVM and even MSCLR straight out the gate. It will likely take years to reach that level of sophistication.

Re:Playing with Go1.1beta2, it's much faster by pjmlp on Tuesday April 09, 2013 @03:58AM (#5516935)
> I also find that HN in general is very quick to downvote comments critical of Go, even well reasoned ones with sources.

I am sure if Go wasn't being done at Google, most hackers would actually ignore it.

Just check how successful the Go like predecessors from the authors were, when working at other companies.

I think the language suffers from an hallo effect.

Re:Playing with Go1.1beta2, it's much faster by enneff on Tuesday April 09, 2013 @04:14AM (#5516968)
If anything, I think that Go has received a disproportionate amount of criticism and skepticism because it was developed at Google. Go is very mature these days - way more mature than most languages ever get - and that's the result of hard work by the contributors, not its pedigree.
Re:Playing with Go1.1beta2, it's much faster by trailfox on Tuesday April 09, 2013 @05:11AM (#5517080)
I've seen posts where "it's from Google" is cited as sufficient explanation for taking an interest in the language. If Go was a random project on GitHub there is very little chance that I would have given it a second look, let alone learning it (which I am presently doing). I have great respect for projects which start out as random GitHub projects and succeed without having the advantage of a name like Google to give them street cred.

Most of the negative Go posts I've seen are to do with limitations of the language and performance relative to JVM languages. As much as I think go has a lot going for it I'm not about to claim that it's anywhere near as expressive as Python or even Scala. There has also been some frustration about denials over the performance gap between Go and the JVM despite very clear data in favor of the JVM. I'm not as bothered by the performance gap as I am about the head-in-the-sand denials. The JVM's have been optimized for 15+ years, so it's ok to admit it may be a few more years before performance can match the JVM.

Re:Playing with Go1.1beta2, it's much faster by enneff on Tuesday April 09, 2013 @05:17AM (#5517097)
> I've seen posts where "it's from Google" is cited as sufficient explanation for taking an interest

That might be enough to draw interest, but what sustains that interest is the quality of the work and the utility of the environment.

> If Go was a random project on GitHub

Where it's hosted is irrelevant. It's about the work. Plenty of active, popular projects are hosted on GitHub. Some of them were just "random projects on GitHub" when they started. What distinguishes them is that there are motivated groups of people working on them.

Re:Playing with Go1.1beta2, it's much faster by sigzero on Tuesday April 09, 2013 @08:14AM (#5517564)
> That might be enough to draw interest

That is pretty much the zinger. If Google hadn't been involved, Go probably wouldn't be were it is at all.

Re:Playing with Go1.1beta2, it's much faster by pjmlp on Tuesday April 09, 2013 @04:38AM (#5517015)
And yet it throws out the window quite a few modern language features.
Re:Playing with Go1.1beta2, it's much faster by iand on Tuesday April 09, 2013 @04:49AM (#5517037)
Which is to be congratulated. If only more languages were as coherent rather than attempting to cater for every possible constituency.

Makes it easier to decide whether Go is the right language choice for the problem at hand. Quite often it won't be and that's fine.

Re:Playing with Go1.1beta2, it's much faster by enneff on Tuesday April 09, 2013 @05:16AM (#5517092)
Re:Playing with Go1.1beta2, it's much faster by ansible on Tuesday April 09, 2013 @03:08PM (#5520394)
I am sure if Go wasn't being done at Google, most hackers would actually ignore it.

I would hope that we hackers would pay at least some attention to any project involving Ken Thompson and Rob Pike though.

Re:Playing with Go1.1beta2, it's much faster by Roboprog on Tuesday April 09, 2013 @09:41AM (#5517956)
Good thing one of the key contributors to the HotSpot JIT is part of the core Go team (please don't ask me to spell the Swiss guy's name). Give them another couple years, Go may well pull up to the same "asymptote" for GC performance, tuning, and such.
Re:Playing with Go1.1beta2, it's much faster by trailfox on Tuesday April 09, 2013 @10:54AM (#5518464)
Re:Playing with Go1.1beta2, it's much faster by voidlogic on Tuesday April 09, 2013 @09:49AM (#5518002)
Why don't you just post the link to Go 1.1 beta 1 vs Java/JVM rather than speculating?

http://benchmarksgame.alioth.debian.org/u64/benchmark.php?te...

Re:Playing with Go1.1beta2, it's much faster by igouy on Tuesday April 09, 2013 @10:22AM (#5518183)
Please check which Go version was used for the measurements `trailfox` pointed to ;-)
Re:Playing with Go1.1beta2, it's much faster by trailfox on Tuesday April 09, 2013 @10:45AM (#5518385)
Good point. It turns out that the quad core benchmarks on 32bit which I linked to are already using Go 1.1beta, so any speed gains for Go 1.1 are already factored in:

http://benchmarksgame.alioth.debian.org/u32q/benchmark.php?t...

The 64 bit quad core benchmark is using go 1.0.3:

http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t...

Re:Playing with Go1.1beta2, it's much faster by voidlogic on Tuesday April 09, 2013 @10:53AM (#5518454)
Go does has known issues and does poorly on 32-bit x86. I would not draw any meaningful conclusions from it about Go in general.
Re:Playing with Go1.1beta2, it's much faster by igouy on Tuesday April 09, 2013 @11:24AM (#5518723)
Would you draw meaningful conclusions from the x64 measurements in-general -- knowing that they don't hold for x86 ;-)
Re:Playing with Go1.1beta2, it's much faster by voidlogic on Tuesday April 09, 2013 @11:36AM (#5518828)
I do see your point, but the vast majority of Go production code runs on Linux/amd64, so yes, that is the most meaningful result.