4 ms·

- "Write once, run everywhere." as the sibling poster mentions. I can build on my Mac, deploy on whatever the server platform is. Snapshot and release builds o

- "Write once, run everywhere." as the sibling poster mentions. I can build on my Mac, deploy on whatever the server platform is. Snapshot and release builds of our build server are distributed via a Nexus-managed repository. So, everyone codes against exactly the same dependencies, regardless of the platform. - Hotswapping/JRebel. - Good interoperability with other languages. E.g. the Typesafe folks implemented Akka in Scala. Java gets it for (well, almost) free. - Easy monitoring and instrumentation. Obviously, there are downsides as well, such as startup times (twofold: starting the VM and Hotspot detection/compilation), preset heap size, expensive JNI (native interface), etc.

dualogy 13y ago
> Write once, run everywhere Well, so Go is "write once, build 3-9x, run anywhere".. close enough ;)
- cthackers 13y ago
  i think i would rather build a binary for each platform and run as fast as possible than to build once and run slow on all platforms.
  - mercurial 13y ago
    Java is a damn memory hog, but for server-side kind of stuff, not really slow.
  - danieldk 13y ago
    Except that Java code typically runs as fast or faster in the JVM than compiled Go code[1]. Of course, Go is still new and gc and gcc-go will be optimized further. But Java bytecode execution is definitely not slow and usually within 2x the execution time of a C implementation, which is faster than the vast majority of other language implementations. [1] At least in the language benchmarks game. Yes, I know that microbenchmarks are not representative, etc. etc. etc. (Until your favorite language is faster ;).)
  - coldtea 13y ago
    Only it's the reverse. Java runs faster than Go.
    - voidlogic 13y ago
      For now, if this continues to narrow it will not be true much longer: http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?test=all&lang=go&lang2=java&data=u64q http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t...
  - brown9-2 13y ago
    This is a false dichotomy.

dualogy 13y ago

> Write once, run everywhere Well, so Go is "write once, build 3-9x, run anywhere".. close enough ;)

cthackers 13y ago
i think i would rather build a binary for each platform and run as fast as possible than to build once and run slow on all platforms.
- mercurial 13y ago
  Java is a damn memory hog, but for server-side kind of stuff, not really slow.
- danieldk 13y ago
  Except that Java code typically runs as fast or faster in the JVM than compiled Go code[1]. Of course, Go is still new and gc and gcc-go will be optimized further. But Java bytecode execution is definitely not slow and usually within 2x the execution time of a C implementation, which is faster than the vast majority of other language implementations. [1] At least in the language benchmarks game. Yes, I know that microbenchmarks are not representative, etc. etc. etc. (Until your favorite language is faster ;).)
- coldtea 13y ago
  Only it's the reverse. Java runs faster than Go.
  - voidlogic 13y ago
    For now, if this continues to narrow it will not be true much longer: http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?test=all&lang=go&lang2=java&data=u64q http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t...
- brown9-2 13y ago
  This is a false dichotomy.