I am, in fact, a Python / C++ user who probably isn't switching to Clojure any time soon (unless I switch jobs).
I still think that these posts are a little light on what exactly the library's cluster story is. Your library, for instance, says "Distributed" right there on the landing page, which is already super helpful for me to know what I'm looking at at a glance.
I should note that ours also isn't "GPU first" but more "GPUs as an addon to your cluster for Deep learning" which is how the resource managers typically used in JVM land like mesos and yarn are treating it.
Stuff like: http://spark.apache.org/news/spark-wins-daytona-gray-sort-10...
Spark makes different assumptions about the computers than what MPI does. "HPC" is 99% of the time some variant of MPI with some sort of special hardware interconnect like infiniband.
It's just in general a different software stack with different assumptions.
Like I said- I work on gpu stuff for the JVM as well, the assumption is different with how the cluster is expected to be setup though.
Usually the folks using MPI and the like either know python or c++ and are fine with that ecosystem where it's already well served often directly from vendors like nvidia and intel.