Put your ear to the ground, and you too will hear it.
My employer is doing the same.
[1] https://github.com/rajasekarv/native_spark
[2] https://medium.com/@rajasekar3eg/fastspark-a-new-fast-native...
I think the situation is similar to c++ where too many features have been added over time.
While with c++ there is a body of compiled recommendations on what not to use and how to write c++, for scala that doesn't really exist.
On the flip side, Scala can be a very pleasant stack to work with if you have right people on the team.
> While with c++ there is a body of compiled recommendations on what not to use and how to write c++, for scala that doesn't really exist.
Principle of least power is what you need.
Not everything is a science paper.
Sure, some companies are moving to other languages, that might be growing quicker than Scala ever was. But this isn't zero-sum.