3 ms·
> Also didn't work out. Are you implying that Scala.js didn't work out? That would be denying the huge success it has within the Scala community. It is notably
by sjrd 10y ago
> Also didn't work out.
Are you implying that Scala.js didn't work out? That would be denying the huge success it has within the Scala community. It is notably supported by most major Scala libraries. To back this by data, it appears 5th in a ranking of Maven artifacts based on the number of artifacts depending on it [1]. Above it are Scala itself, Specs2, Akka and scoverage.
Scala/.NET didn't work out because we never managed to reconcile the type system of Scala with that of the CLR. For JavaScript, we did manage that, and pretty easily: it's much easier to erase all types than converting from an advanced type system to another advanced type system.
[1] https://scaladex.scala-lang.org/search?q=&page=1&sort=dependentCount https://scaladex.scala-lang.org/search?q=&page=1&sort=depend...
- paulddraper 10y ago> Are you implying that Scala.js didn't work out? Er, definitely not. Bad mis-statement on my part. Should have said "also had challenges." And you're correct about type erasure. Scala/Scala.js/SBT are my tools of choice for web apps. I gave a talk "Scale your code with Scala.js" at Fluent last year https://conferences.oreilly.com/fluent/fl-ca-2016/public/schedule/detail/46780 https://conferences.oreilly.com/fluent/fl-ca-2016/public/sch...
- sjrd 10y agoCool! I had completely misunderstood your earlier comment ;)