4 ms·

I wouldn't jump on the Scala 3 ship just yet. Maybe if mostly a learning project but not for an important part. Whilst it was not a surprise release there will

by flurdy 5y ago

I wouldn't jump on the Scala 3 ship just yet. Maybe if mostly a learning project but not for an important part. Whilst it was not a surprise release there will be long time until a majority of the libraries and frameworks will also work with it. The big ones are mostly there, but there are lots of smaller ones that are not and there will be teething problems, even after a long alpha-beta-rc train. Scala 2.13 is still great.

Scarbutt 5y ago
Looks like many libs already support Scala3: https://index.scala-lang.org/search?targetTypes=jvm&scalaVersions=scala3&q=*&page=1 https://index.scala-lang.org/search?targetTypes=jvm&scalaVer...
- virtualwhys 5y ago
  Not sure what Play Framework is doing at the top of the list, will most likely be many months before a Scala 3 supported version is released. Same for Spark, DB libraries, Akka, etc. Basically everything with large dependency graphs that depend on macros or removed Scala 2 features (e.g. abstract type projections, arghhhh) will take significant time to port over to Scala 3. What has had Scala 3 support from early on in the release cycle are the FP/Typelevel projects, which are obsessively maintained by the I'll-sleep-when-I'm-dead FP crowd.
  - ahel 5y ago
    Is Play Framework still used/developed? Haven't seen any progress from performance in the last years. Happy to get corrected, though.
    - flurdy 5y ago
      It probably is still the most used framework, probably by quite a margin. Whilst I mostly use Http4s these days I would guess the majority of new projects still pick Play. I would say 60% but would not be surprised if the actual number is 95%. The silent majority just need to chuck out another internal app quickly and Play is great for that. It also looks like it is still heavily developed as 2.9 is released soon. As for performance, shrug.
kag0 5y ago
I agree. But would note that scala 3 is compatible with 2.13 libraries, so long as they don't use scala 2 macros. I think scala 3 is ready to go for production use, but it did come out yesterday. So waiting a tick would be prudent.

by flurdy 5y ago

Scarbutt 5y ago

Looks like many libs already support Scala3: https://index.scala-lang.org/search?targetTypes=jvm&scalaVersions=scala3&q=*&page=1 https://index.scala-lang.org/search?targetTypes=jvm&scalaVer...

virtualwhys 5y ago
Not sure what Play Framework is doing at the top of the list, will most likely be many months before a Scala 3 supported version is released. Same for Spark, DB libraries, Akka, etc. Basically everything with large dependency graphs that depend on macros or removed Scala 2 features (e.g. abstract type projections, arghhhh) will take significant time to port over to Scala 3. What has had Scala 3 support from early on in the release cycle are the FP/Typelevel projects, which are obsessively maintained by the I'll-sleep-when-I'm-dead FP crowd.
- ahel 5y ago
  Is Play Framework still used/developed? Haven't seen any progress from performance in the last years. Happy to get corrected, though.
  - flurdy 5y ago
    It probably is still the most used framework, probably by quite a margin. Whilst I mostly use Http4s these days I would guess the majority of new projects still pick Play. I would say 60% but would not be surprised if the actual number is 95%. The silent majority just need to chuck out another internal app quickly and Play is great for that. It also looks like it is still heavily developed as 2.9 is released soon. As for performance, shrug.

kag0 5y ago

I agree. But would note that scala 3 is compatible with 2.13 libraries, so long as they don't use scala 2 macros. I think scala 3 is ready to go for production use, but it did come out yesterday. So waiting a tick would be prudent.