3 ms·

Scala is great for statically typed functional programming. It can be as pure as Haskell, but with the escape hatch of not requiring that purity at the language

Scala is great for statically typed functional programming. It can be as pure as Haskell, but with the escape hatch of not requiring that purity at the language level. With Scala 3 coming out next year it will become more approachable to developers that find Haskell and OCaml off putting (and has already solved the "python 3 problem"!). As for scala-native, it gets past the major draw backs of the JVM: startup speed, memory size, and Oracle. From applets in 2002 to kubernetes sidecars and aws lambda today, the JVM refuses to optimize for these things.

pjmlp 7y ago
What a joke. Currently Scala.Native still performs poorly than Scala JVM. Since 2000 anyone that cared about AOT in Java had quite a few commercial Java vendors that offered AOT on their JDKs, Oracle and IBM were two of them. Project Panama, Valhalla, Metropolis and Graal are proof that Java community does care to optimize for these things.
- densh 7y ago
  > Currently Scala.Native still performs poorly than Scala JVM. This is factually incorrect [1]. 0.4.0 series is shipping with brand new optimizer (as of M1) and soon a parallel garbage collector (M3). Both contribute to major performance overhaul compared to the current stable 0.3 branch (see benchmarks on the link below). [1] https://github.com/scala-native/scala-native/releases/tag/v0.4.0-M2 https://github.com/scala-native/scala-native/releases/tag/v0...
  - pjmlp 7y ago
    Benchmarks against all major Java implementations?
- cheriot 7y ago
  So developers can choose to have the batteries included or to pay a vendor. I hear signing contracts with IBM and Oracle is a great experience. Is that the joke? > proof that Java community does care Oh, the community wants them. It's been Sun then Oracle and now the OpenJDK project that has never prioritized these things and that's the runtime 99% of JVM shops run.
  - pjmlp 7y ago
    The sad joke, when comparing with other professions, is wanting to be payed while refusing to pay others for the tooling one uses.
    - cheriot 7y ago
      I happily pay for a number of excellent tools. I also have no interest in doing business with IBM and Oracle again.

pjmlp 7y ago

What a joke. Currently Scala.Native still performs poorly than Scala JVM. Since 2000 anyone that cared about AOT in Java had quite a few commercial Java vendors that offered AOT on their JDKs, Oracle and IBM were two of them. Project Panama, Valhalla, Metropolis and Graal are proof that Java community does care to optimize for these things.

densh 7y ago
> Currently Scala.Native still performs poorly than Scala JVM. This is factually incorrect [1]. 0.4.0 series is shipping with brand new optimizer (as of M1) and soon a parallel garbage collector (M3). Both contribute to major performance overhaul compared to the current stable 0.3 branch (see benchmarks on the link below). [1] https://github.com/scala-native/scala-native/releases/tag/v0.4.0-M2 https://github.com/scala-native/scala-native/releases/tag/v0...
- pjmlp 7y ago
  Benchmarks against all major Java implementations?
cheriot 7y ago
So developers can choose to have the batteries included or to pay a vendor. I hear signing contracts with IBM and Oracle is a great experience. Is that the joke? > proof that Java community does care Oh, the community wants them. It's been Sun then Oracle and now the OpenJDK project that has never prioritized these things and that's the runtime 99% of JVM shops run.
- pjmlp 7y ago
  The sad joke, when comparing with other professions, is wanting to be payed while refusing to pay others for the tooling one uses.
  - cheriot 7y ago
    I happily pay for a number of excellent tools. I also have no interest in doing business with IBM and Oracle again.