3 ms·

I worked at a Scala shop about 10 years ago. Everyone had their own preferred "dialect", kind of like C++, resulting in too much whining and complaining during

I worked at a Scala shop about 10 years ago. Everyone had their own preferred "dialect", kind of like C++, resulting in too much whining and complaining during code reviews. IMHO, the language is too complex. Also, the compiler was slow, and the IDE support was plain awful (Eclipse was especially bad, IntelliJ was better.) Keep in mind this was over a decade now, so I'm sure things have improved.

mjr00 5y ago
This was my experience as well. I worked at a place that used Scala primarily in the "better Java" style and enjoyed the language a lot. I moved to a different company and the lead programmer there was a functional purist who insisted on putting scalaz/cats into everything and using Scala as Haskell lite, despite it really not being appropriate for the use case. It really soured me on the language.
vips7L 5y ago
There’s no bigger productivity killer than scalac and sbt.
- icedchai 5y ago
  Is it still that way? I've thought about taking another look at it for personal projects.
  - dboreham 5y ago
    Not parent but yes it is.
  - vips7L 5y ago
    By the time the sbt shell starts I swear to god maven would have my project fully packaged.
- herbstein 5y ago
  I work in a Scala shop with 500k lines of Scala. We're moving to a Bazel-based development workflow because SBT is a slog and doesn't handle incremental compilation well at all.