Ocaml also has a long standing claim to being an oo plus functional language for the future that hasn’t seen a lot of uptake. It would have been heartening and reassuring for the author to explore more candidates than Scala.
It's not so much that, but rather that OCaml's dominant paradigm of modules and functions is just so powerful that you almost never need OOP. But when you do, it's super useful to have.
I disagree. OO features are very heavily used in Scala and the languages it influenced. TypeScript and Swift particularly come to mind. I think the key here is that Scala paved the way for type systems capable of modeling OOP and FP idioms, cleaning up what OCaml attempted. Although one could argue that none of the other post-Scala languages inherit the full toolkit of typed FP features as much as Scala (pattern matching, everything is an expression, true ADTs).
The complaints I remember about ocaml the last time I checked it out were related to multithreading. No idea if that's changed. But I do see ocaml very often in use to write a compiler, especially for languages that aren't yet self-compiling, most recently when looking into Haxe.
Node.js, Python, and Ruby are single-threaded. They all have ways to achieve concurrency and multi-process usage right now, and so does OCaml. I get it, people really want OCaml multicore–and it's coming–but that by itself is not stopping OCaml from being an industrial-strength, production-ready language right now.
