8 ms·

Not only that but it's an easier to find out what is going on inside a JVM versus a static Go binary. It's not all about performance.

• pron 12y ago
  Absolutely, but it also has better performance than Go.
  • NateDad 12y ago
    For some things. For many things they are pretty equivalent. http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?test=all&lang=go&lang2=java&data=u64q#faster-programs-measurements http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t... And Java uses a lot more memory, which is what the article was talking about adversely impacting execution speed.
    • pling 12y ago
      It uses memory differently is probably a better explanation.
    • igouy 12y ago
      http://benchmarksgame.alioth.debian.org/play.php#whymemory http://benchmarksgame.alioth.debian.org/play.php#whymemory
    • waps 12y ago
      Beating java in memory usage is like beating a tied-up blindfolded turtle you gave cement shoes and dropped into a toxic vat in the 100 meters walking. You know, if the turtle was disqualified ahead of time. Now let's compare how many lines it takes to read in 2 csvs into structs, sort them by their normals and write their vector products out into a new file. I bet java will do < 100 lines and go will be 10 files and > 1000 lines. It'd be about as honest.