Anytime you're looking at a wish-list of requirements one or some of them might give way for the sake of advances in the other. The OP wants: static typing, concurrency, good tooling, speed/simplicity in a web framework, non-reliance on big IDEs.
If OP were to look at using Clojure/Luminus they might find that the combination of everything except the static typing was sufficient to overcome the lack of static typing (also something like Prismatic Schema to mitigate types might help). I haven't messed around with it enough to say, but there is also JVM interop with clojure so one could write the most type-concerned components in Java (or even in Scala).
tldr: failing one requirement of many isn't necessarily a reason to not offer an option if it succeeds on many others.
