News for hackers. Stuff that matters.
Re:Things that make Go fast by seanmcdirmid on Saturday June 07, 2014 @05:40PM (#7863187)
That is the weird part of the essay...they talk about why Go is faster than Java, without mentioning that it really isn't.
Re:Things that make Go fast by stcredzero on Saturday June 07, 2014 @07:29PM (#7863451)
[Citation Needed]

Just re-read it. Again, I didn't see anyplace where it's actually said that Go is faster than Java. I can see many places where someone touchy and defensive might take it that way, however. Either the apparent knee-jerk reaction is a deliberate attempt to troll by creating a false argument, or it's simply a cringe worthy false argument worthy of a Picard meme.

Re:Things that make Go fast by seanmcdirmid on Sunday June 08, 2014 @03:24AM (#7864189)
A blog post talking about why to use Go...for performance...and here is how it is better than Java about performance, even though it's not really better than Java. I don't care about Java, my language of choice is C#, but this smacks of the worst kind of anti-logic promotion. It seems to be quite endemic in the Go community also.
Re:Things that make Go fast by stcredzero on Sunday June 08, 2014 @09:17AM (#7864592)
Again, is this a deliberate troll, or is it intellectual sloppiness? The post talks about why Go is fast. There are memory footprint comparisons. AFAICT, There are no language speed comparisons.

There is only text that a genuinely touchy and defensive person or a troll might misconstrue. Did someone steal seanmcdirmid's HN password?

Re:Things that make Go fast by seanmcdirmid on Sunday June 08, 2014 @11:45AM (#7864955)
If one talks about why Go is fast, and then compares techniques against other languages ANYWAYS, what the heck is the reader supposed to think? In an academic paper, this would be torpedoed right away: you aren't allowed to take the 5th if you want to beg the question.
Re:Things that make Go fast by stcredzero on Sunday June 08, 2014 @02:09PM (#7865358)
If one talks about why Go is fast, and then compares techniques against other languages ANYWAYS, what the heck is the reader supposed to think?

That a short discussion of language feature implementation techniques is provided as a point of comparison with regards to different types of overheads?

In an academic paper, this would be torpedoed right away

Well, since I read "this" in the context of this sentence as an assertion imagined by you and unsupported by facts, then yes, you are obviously right. That would be torpedoed. Note that it's not a product of who you thought it was.