sjrd

27 ms·

1. 301.▲
   by sjrd 13y ago

   True, but its main target is definitely the browser. The stand-alone interpreter of Node.js can run code written in Scala.js, and is actually used for benchmarks (along with d8) [1]. However, Scala.js does not emit Node.js modules, nor does
2. 302.▲
   by sjrd 13y ago

   It's basically equivalent to Scala for the compilation itself (no noticeable difference). But the browser refresh in dev mode can take up to 5 seconds (or down to under 1 sec, depends on the machine). There is a tool that helps with th
3. 303.▲
   by sjrd 13y ago

   The video recording is now available! http://www.parleys.com/play/51c380bfe4b0ed8770356866
4. 304.▲
   by sjrd 13y ago

   If you ask me, this is all about (b) if you consider only JavaScript vs Scala.js. If you compare Scala.js to similar languages (CoffeeScript, TypeScript, ClojureScript to name a few), it definitely helps to have the same language both on se
5. 305.▲
   by sjrd 13y ago

   Hi, The slides shown there are, well, slides. They are meant to support a talk , and that talk addressed your comments, at least partly. It is also worth noting that it was Scala Days, and as such I took it for (almost) granted that the au
6. 306.▲
   by sjrd 13y ago

   Hi, Quick comment from the author: #1 has already been addressed by emitting Source Maps. With a supporting browser, you can debug your Scala.js application easily. You get positions in the original source code, breakpoints in the original