In the C -> C++ -> Java -> Scala progression Java was a gigantic golang-style detour from a multi paradigm language. STL had so much power and a lot of it can b

In the C -> C++ -> Java -> Scala progression Java was a gigantic golang-style detour from a multi paradigm language. STL had so much power and a lot of it can be attributed to quasi-FP abstractions. The first few posts in Bartosz Milewski's blog showed the same examples in both C++ and Haskell. What surprises me is that even among those lucky to work on a powerful platform such as the JVM or .NET it's more typical to stick to a single language. In my mind it'd be more natural to write Java/Kotlin/C# when you want imperative abstractions and Scala/F# when you are in mood for FP. The same platform/libraries, the same IDE/toolchain, only the syntax/abstractions differ. But we know that Scala and F# adoption is nowhere near what some of us would hope for. We also know that the ecosystem fragments immediately and Scala projects don't share [m]any libraries with Java ones for example. So mixing the two languages in one system is mostly about wrapping some legacy code. The "worse is better" essay touched upon some deep truth.