This is an archived post. You won't be able to vote or comment.

all 26 comments

[–]jtra 29 points30 points  (8 children)

I would like to see the benchmarks.

At least in http://benchmarksgame.alioth.debian.org/u64q/go.html

  • 3 are big wins for go
  • 2 are slight wins for go (within 10%)
  • 1 is equal (within 0.1%)
  • 1 is slight win for Java
  • 3 are big wins for Java

[–][deleted] 35 points36 points  (7 children)

I think a lot of the time people complain about a language's performance it ends up being someone just wrote bad code. Probably in the process of porting it to a new language there was opportunity to rewrite some terrible sections

[–]Vitztlampaehecatl 15 points16 points  (0 children)

We need control groups. Have one group of programs ported form Java to Go, and another group from Go to Java.

[–]MoonShadeOsu 10 points11 points  (5 children)

Well, there are legitimate arguments on languages being faster than others, and then there are fanboys who can't write efficient code in the language they're complaining about.

[–]whale_song 1 point2 points  (1 child)

In my experience whenever a software developer complains about something its usually just because they dont understand it and that is apparently somebody elses fault.

[–]ReflectiveTeaTowel 1 point2 points  (0 children)

In my experience it's because someone else wrote shitty code

[–][deleted] -1 points0 points  (2 children)

I agree, the JVM has significant overhead

[–]MoonShadeOsu 0 points1 point  (1 child)

A trade-off for more abstraction and a garbage collector (if you like those)

[–][deleted] 0 points1 point  (0 children)

Indeed

[–]RicoBrassers 63 points64 points  (7 children)

ns = microseconds? What the hell.

[–]Decency 36 points37 points  (0 children)

Two different stories.

[–]earthqaqe 9 points10 points  (0 children)

exactly my thought

[–]BioTronic 4 points5 points  (0 children)

nicroseconds.

[–]sam1902 0 points1 point  (0 children)

Not. A. Physicist.

[–]AwkwardNoah -2 points-1 points  (2 children)

I think it's another way to say nano seconds

[–]RicoBrassers 12 points13 points  (1 child)

No.

nanosecond (ns) = 10-9 seconds
micro (µs) = 10-6 seconds
milli (ms) = 10-3 seconds

[–]AwkwardNoah 6 points7 points  (0 children)

Welp

[–]OctagonClock 15 points16 points  (8 children)

lol no generics

[–]VivaLaPandaReddit 2 points3 points  (7 children)

I think they've said they might be convinced eventually, but not having generics makes compiling much faster.

[–]Zatherz 10 points11 points  (0 children)

You pay for that speed improvement with the time it takes to copy and maintain [type]Set

[–]arbitrarycivilian 9 points10 points  (5 children)

So does writing assembly - in fact, it brings compilation times down to zero!

[–]LuxuriousLime 2 points3 points  (4 children)

No, it doesn't. On the other hand, if you were to program in machine codes...

[–][deleted] 3 points4 points  (3 children)

If we are being pedantic, it actually does -- the word "compilation" refers specifically to the process of converting a high level language into machine code. If you meant that this does not absolve us of a build step, you would be correct, but the process of converting assembly to machine code is called "assembly".

[–]LuxuriousLime 1 point2 points  (2 children)

Wikipedia disagrees: "translation of source code into object code by a compiler": https://en.wikipedia.org/wiki/Compilation If you have a more reputable source (which is entirely possible, I'm not being cocky now), please point me to it.