I'm not a Java developer, and I haven't even read about higher kinded types or typeclasses (the theory side of programming is my weakness); but you picked my curiosity with this.
Can you elaborate how concurrency done this way would look in Java?
> Almost everything there
Everything. But the mere presence of "equivalents" doesn't make pure functional programming less valuable.
My view has been that reinventing imperative programming (IO monad) on math (pure FP) on imperative programming (the machine) brings me no benefit.
For monofunctors: reliable error handling, an ability to re-interpret the same IO structure multiple times, better reasoning during refactorings due to referential transparency.
For bifunctors: the above plus explicit domain (expected) error encoding and even more reliable error handling.
That's another huge effort which delivered us an imperfect abstraction.
I would prefer to have HKTs and typeclasses, so I may implement my own IO monad.