2 ms·
Pick Clojure, Scala or JRuby instead of Java if you need to start off on the JVM, to hedge against this risk.
by fulafel 8y ago
Pick Clojure, Scala or JRuby instead of Java if you need to start off on the JVM, to hedge against this risk.
- int_19h 8y agoHow does this hedge the risks? Those are still built on top of the JDK.
- fulafel 8y agoYou can get off the JDK if needed, because there are good non-JVM implementations of those languages.
- flurdy 8y agoCurrently primarily on the JDK . But enough abstraction to migrate. Scala, for example, has a mature scala.js VM and an emerging Scala Native VM. [1] http://www.scala-js.org http://www.scala-js.org [2] http://www.scala-native.org http://www.scala-native.org
- threeseed 8y agoI do a lot of development in ScalaJS. And what you are talking about is just ridiculous. There are very few real world (if any) Scala projects that don't rely on least some Java based libraries. Either directly or through transitive dependencies.
- fulafel 8y agoIf it's anything like Clojure/ClojureScript, the port would require work but be straightforward in most cases. Many people already use ClojureScript on Node instead of JVM Clojure. If you rely on JVM-only libraries for your core domain functionality, things become harder of course.