Re:Scala – The good, the bad and the very ugly
by frowaway001 on Tuesday October 07, 2014 @02:00PM
(#8422794)
Reliability, performance, maturity, instrumentation, diagnostics.
Just picking one example from the list, performance: How is GHC's runtime dealing with 100GB+ heaps?
Re:Scala – The good, the bad and the very ugly
by sixbrx on Tuesday October 07, 2014 @03:19PM
(#8423349)
Do the Oracle or OpenJDK JVMs deal well with heaps that large? I have no interest in other JVMs because my employer would not consider switching and I can't say I blame them.
Re:Scala – The good, the bad and the very ugly
by kasey_junk on Tuesday October 07, 2014 @04:45PM
(#8423915)
It depends on what you mean by "deal well with heaps that large". You can certainly set them that large with no problems. But given your memory patterns they can cause dramatically bad GC times.
Re:Scala – The good, the bad and the very ugly
by frowaway001 on Tuesday October 07, 2014 @06:12PM
(#8424310)
Yes. It's routinely done.
For Haskell at least, the GHC runtime is getting pretty good, and seems to have at least basic tools for GC analysis etc. I'm ignorant of MLs so perhaps someone can speak to their status.
Of course there's the much-touted "Java Ecosystem" but it's looking crustier than ever methinks. Maven?? Blech! Also, it doesn't seem wise anymore to build a website on Servlets/JSP/SpringMVC etc, esp. if you want to attract devs. Rest APIs maybe.
What's the killer feature these days recommending the JVM?