News for hackers. Stuff that matters.
Re:The JVM situation by peter_l_downs on Tuesday June 18, 2013 @08:24PM (#5902917)
Prolly the biggest advantage of the JVM in my opinion was pointed out by "[email protected]":

    > The one thing I like about the jvm is that I can compile 
    > and package code on one platform and deploy to another 
    > without worrying about anything but the fact that the jvm 
    > is installed.
Solves so many headaches!
Re:The JVM situation by tieTYT on Tuesday June 18, 2013 @08:33PM (#5902950)
Yes, and for how good Haskell is as a LANGUAGE, it sucks at this very important feature (assuming you want to use a 3rd party library).
Re:The JVM situation by michaelsbradley on Tuesday June 18, 2013 @09:03PM (#5903074)
There's always Frege:

https://github.com/Frege/frege

But it's definitely a work in progress.

Re:The JVM situation by mrhonza on Tuesday June 18, 2013 @09:17PM (#5903156)
Yes, I agree that uberjars are a great thing when it comes to the JVM ecosystem. However, with the advent of projects like docker, I can't help but think that this reasoning is now obsolete. You can write your app in Go, Rust or Haskell and deploy it inside a container that you provide. You control the environment that it runs in.
Re:The JVM situation by mjn on Tuesday June 18, 2013 @08:41PM (#5902975)
Sun used to use the catchy slogan "write once, run anywhere" to refer to this property...
Re:The JVM situation by yumraj on Tuesday June 18, 2013 @08:32PM (#5902945)
While it's not the same thing, 'go' can compile for multiple platforms, and then you can deploy appropriate binaries on another OS as long as 'go' is installed.
Re:The JVM situation by burntsushi on Tuesday June 18, 2013 @09:07PM (#5903094)
> and then you can deploy appropriate binaries on another OS as long as 'go' is installed.

Nope. Go does not need to be installed for a binary produced by the `gc` compiler to run.