| ▲ | hocuspocus 4 hours ago | |||||||
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. | ||||||||
| ▲ | hnaccount19293 3 hours ago | parent [-] | |||||||
> Arguably Rust is worse, and it doesn't impact its uptake. I've been in both communities and this isn't my experience at all. There was a significant period of time in the Scala community where you'd get insulted constantly if you didn't buy into an extremely rigid purely functional programming mindset. Even Odersky and Li Haoyi were continuously berated. The Scala community moderators were far too slow at dealing with these people and a ton of people left because of it. The Rust community is amazingly welcoming in comparison and the constant vitriolic flaming that occurred in the Scala community simply wouldn't be tolerated. | ||||||||
| ||||||||