The rationale for using Scala.js
Dec. 19th, 2016 04:44 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jducoeur[Mainly for the programmers, and this time mainly for folks who have to touch web browsers.]
I'm currently catching up on old articles I've bookmarked to read later (more links may come), and I just read through this marvelous discussion of Scala.js, the Scala-to-Javascript compiler. In it, Li Haoyi (one of the first serious users of Scala.js, and one of the most important ecosystem developers) explains why Scala.js is not only one of the best ways to develop for the Web, but why he decided from very early on that it was likely to *become* one of the best.
It's a compelling argument, and after 2+ years of heavy Scala.js use, I totally agree: it's the first environment for developing this stuff that I've actually *liked*. The article is long but recommended, and I'm happy to answer any questions...
I'm currently catching up on old articles I've bookmarked to read later (more links may come), and I just read through this marvelous discussion of Scala.js, the Scala-to-Javascript compiler. In it, Li Haoyi (one of the first serious users of Scala.js, and one of the most important ecosystem developers) explains why Scala.js is not only one of the best ways to develop for the Web, but why he decided from very early on that it was likely to *become* one of the best.
It's a compelling argument, and after 2+ years of heavy Scala.js use, I totally agree: it's the first environment for developing this stuff that I've actually *liked*. The article is long but recommended, and I'm happy to answer any questions...