I did a couple of projects where I'd pick up a broken Scala system and fix it, it was usually "screw around for a week in Scala and it (1) still has race conditions and doesn't give the same answer every time, (2) has totally busted error handling (they seemed to think saying the word 'monad' meant you didn't have to think about error handling) and (3) used at most 2 CPUs out of 8."
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)