5 ms·
At least when I used it ~2 years ago: an extremely complex type system with a huge learning curve (unless you're going to just write Java in Scala), poor docume
by benhoyt 6y ago
At least when I used it ~2 years ago: an extremely complex type system with a huge learning curve (unless you're going to just write Java in Scala), poor documentation, and a very slow compiler. That's to say nothing of the JVM-based runtime.
- doliveira 6y agoI got really frustrated one of these days because I reached the 20-something limit for fields in a case class and I had to change a lot of my architecture. It was a Spark job so I needed all those fields in that structure. Not sure if that's because I'm a beginner or if it's just Spark itself, but Scala errors are impossible to decrypt.
- valenterry 6y agoAh yeah, that was really a stupid limit. Time to bump Scala to version 3 so that you don't have the 22 case class field limit anymore. :) See here: https://dotty.epfl.ch/docs/reference/dropped-features/limit22.html https://dotty.epfl.ch/docs/reference/dropped-features/limit2...
- valenterry 6y ago> unless you're going to just write Java in Scala That is what I mean though - but I would replace "Java" with python here. Just stay away from all the complexity and write python code. It's pretty simple and some people argue it's the better way to use Scala.