Or you could use Scala
Rewriting it in Java with ExecutorService would solve all those problems in like... 20 minutes.
But yeah, I think a lot of people would think Ferocity combines all the awful things about Java (verbosity) and Common Lisp (the "write once never edit" problem of metaprogramming)
Blocked threads are seriously bad for performance. Yes, Java 21 project Loom will help with that (finally), if people get with the program.
There aren't any race conditions, because our classes and data model are fully immutable.
The problem with our legacy servers was that the original devs didn't know what monads were, and decided not to use them. Error handling is now great, by using...
you guessed it, monads.