Scala 2.12.0 is now available
scala-lang.org
Scala 2.12.0 is now available
1–10 of 78 posts
Re: Scala 2.12.0 is now available
#2Re: Scala 2.12.0 is now available
#3Re: Scala 2.12.0 is now available
#4Re: Scala 2.12.0 is now available
#5This is great because the generated bytecode is smaller and more resistant to binary compatibility issues. Scala has had problems with binary compatibility because its features don't map that well on top of the JVM and traits have been very problematic, so thankfully now we have a more efficient encoding. Having SAM support is also good for both Java devs wanting to use Scala libraries and for Scala devs wanting to use Java libraries.
But this also means that Scala 2.11 should be a long-term support version, because even though Java 6 and 7 have reached end of life, the world is not ready to fully commit to Java 8, as sadly there are projects like Android that are holding us back.
Scala 2.12 is a big achievement, with many changes under the hood. I'm happy to finally see it released. Kudos to those involved.
Re: Scala 2.12.0 is now available
#6Just removing this `body { color: #586E75 }` altogether makes your page readable.
Re: Scala 2.12.0 is now available
#7Great stuff but can you please scale up font contrast a bit? Just removing this `body { color: #586E75 }` altogether makes your page readable.
Re: Scala 2.12.0 is now available
#8The right-biased Either, and the partial unification support that it builds on, are a much needed and much appreciated improvement. Really looking forward to trying out this release.
Re: Scala 2.12.0 is now available
#9More details http://get-scala.org/2.12
Re: Scala 2.12.0 is now available
#10This is the version of Scala that breaks compatibility with Java 6 in the generated bytecode, by making use of Java 8's features, like invokedynamic, default interface methods and integration with SAM types. This is great because the generated bytecode is smaller and more resistant to binary compatibility issues. Scala has had problems with binary compatibility because its features don't map that well on top of the J…
And GAE standard environment. :(