| ▲ | wk_end 4 hours ago | ||||||||||||||||
My impression is that, rightly or wrongly, it developed a bit of a negative reputation in various ways - too esoteric, slow builds, toxic community, etc. - so people stayed away from it. And meanwhile, Java the language improved and Kotlin came along as (arguably) the better better Java, so there became less of a need for it. | |||||||||||||||||
| ▲ | hocuspocus 4 hours ago | parent | next [-] | ||||||||||||||||
I'm pretty sure most companies don't care nor are aware about the community drama. Arguably Rust is worse, and it doesn't impact its uptake. Scala was sold through Akka and Spark, solving pretty complex technical challenges that are less relevant nowadays. In fact if you can avoid Akka and Spark, do. A lot of companies followed the hype without investing in the developer experience. Tech debt hurts more in Scala than in a bigger, slow moving language. After typical turnover, you get teams inheriting unmaintainable codebases. This leaves a bad impression. It can be avoided, Twitter built world-class SOA with Finagle, as well as a complete layer of libraries on top of Hadoop, at a time where the Scala ecosystem was even rougher. The fact Databricks doesn't care much about the language also did tremendous damage, forcing the community to cross-build against very outdated versions of Scala. In short, Scala was never a better Java and adopters who thought otherwise invariably got burned. | |||||||||||||||||
| |||||||||||||||||
| ▲ | jghn 2 hours ago | parent | prev | next [-] | ||||||||||||||||
Yes. The list of reasons is long, but at the end of the day the Haskell on the JVM crowd moved on to other things, and the people who just wanted Java++ moved to Katlin. And that was most of the audience. | |||||||||||||||||
| ▲ | morkalork 4 hours ago | parent | prev [-] | ||||||||||||||||
Felt weirdly gate-kept as well. | |||||||||||||||||