2 ms·
> it was too difficult to embed a JVM-based language into other runtimes and languages In addition to the JVM, Scala has had JS [1] and native (via LLVM) [2] t
by paulddraper 7y ago
> it was too difficult to embed a JVM-based language into other runtimes and languages
In addition to the JVM, Scala has had JS [1] and native (via LLVM) [2] targets for years.
(And that's not even mentioning any second-order compilations; e.g. Scala -> JVM bytecode -> native)
There's a number of reasons to not choose Scala, but portability is far from one of them.
[1] https://www.scala-js.org https://www.scala-js.org
[2] http://www.scala-native.org http://www.scala-native.org
- pacala 7y agoThe library ecosystem is different between JVM/JS/Native. Porting across runtimes may require more work than just changing the compilation target.
- paulddraper 7y agoThat's true. If you want it across all platforms, you are restricted to the Scala ecosystem, and can't use Java and JS ecosystems.