The problem is that those are f**king difficult problems to solve. Regardless of how you approach them. No tool or paradigm will make them easy, it may make a p

The problem is that those are f**king difficult problems to solve. Regardless of how you approach them. No tool or paradigm will make them easy, it may make a part of them easier (at some other cost somewhere else), but by no means will make it easy. Building large scale, low latency systems is really hard. Handling concurrency and shared state is hard. Heck, even functional programming is hard to grok for most people. The evidence is in its popularity (or lack of it). There's no large mystery why we all are not using functional programming exclusively: because it's hard. Imperative, with all it's drawbacks it's easier to grasp and closer to how hardware works. Most people find it more natural, there's no big conspiracy. But (there's always a "but"), the functional paradigm is essential to solve all those hard problems. It provides many tools where many common pitfalls are essentially avoided, but gaining a comfortable grasp of those tools takes work and it's not easy as many claim. They seem easy after you've had the "aha!" moment, but it's like advanced math, getting there takes time and a certain proclivity to it. Once you develop some sort of intuition, you tend to forget the effort it took to gain it. In any case, I love languages and new ideas, so I hope he succeeds (or fails in an interesting way where we learn something new).