4 ms·
For those from Java world wanting to write client-side, there is obviously also GWT[1] and another interesting option is TeaVM[2]. Interesting part of TeaVM is
by prohor 11y ago
For those from Java world wanting to write client-side, there is obviously also GWT[1] and another interesting option is TeaVM[2]. Interesting part of TeaVM is that it translates bytecode, so I guess it could do Scala as well. But I've never used it, so cannot recommend really.
1. http://www.gwtproject.org/ http://www.gwtproject.org/
2. https://github.com/konsoletyper/teavm https://github.com/konsoletyper/teavm
- pjmlp 11y agoI already write client side with Swing and JavaFX....
- sjrd 11y agoGWT doesn't do Scala. That puts it out of the equation as far as most Scala.js developers are concerned. Also, it's interoperability story is seriously lacking behind Scala.js. TeaVM is a fun and impressive project. However, although they can compile Scala-emitted bytecode (since a few weeks ago [1]), that's not their main focus. They are unlikely to ever optimize Scala code as well as Scala.js, because Scala.js focuses on optimizing idiomatic Scala. They do have an undeniable advantage over Scala.js, though, which is that they can also compile Java libraries used by a Scala program. [1] https://groups.google.com/d/msg/scala-js/3jbX9ajIbHM/MbLWIqpkBgAJ https://groups.google.com/d/msg/scala-js/3jbX9ajIbHM/MbLWIqp...
- merb 11y agoScala's biggest concern is compilation time. However when comparing GWT and ScalaJS, mostly ScalaJS pulls ahead. So Java -> Js or Scala -> Js you would definitly prefer Scala.