[eshvk]

> (2) You may need to use a particular JVM library (there's a lot of really good ones).

I would love to hear some examples? It always appears to me that you could use JVM on the backend and have robust services that communicate with the front end layer (flask/tornado/whatever). However, I would be open to hearing something new.

> (3) Some spaces of the open-source ecosystem are largely written with JVM languages (especially in the data space: Hadoop, Mahout, Spark, etc). If your team is heavily dependent on one of those spaces you may choose the JVM for your applications simply to focus your teams knowledge on one platform.

From the data perspective, in all the places I have been, the data has been sliced up, processed, put through models and is available either as services or SQL databases. After that, there has never been a strong enough rationale not to use something else for the web server. I mean, from my understanding, you will end up having to write JS for the browser side of things. So you are no longer tooling on one platform any more, are you?