jducoeur
By now, I'm at the point where adding a whole new API and making use of it in the client can be done in minutes -- having Scala end-to-end is a huge win. And having static type checking for the client code means that there are far fewer bugs, so coding the client itself is much quicker and less frustrating. Really, it's the first time in 20+ years that I've enjoyed web programming.
That's just a tiny startup (https://www.querki.net/help/#What-is-Querki -- note that everything you see there is Scala.js), but I don't think it would have been possible without SJS...
Including the standard Scala.js prelude (100-200k), that currently clocks in at a bit under a megabyte. That's quite reasonable for a program of its complexity, and loads pretty fast. And once that is loaded and in the browser cache, the UI is lightning fast afterwards...
For example, I'm building a product with a moderately complex front end. I'm using about 10-15 JS libraries, including JQuery and JQuery UI, as part of that. I just write a strongly-typed facade on top of each library, describing what it does (which takes just a few minutes), and I'm off to the races. Similarly, other folks are doing things like writing Scala.js adapters for React, Angular, and so on.
So Scala.js isn't in competition with the existing JS libraries. Far from it: I think of it as a much better way to use the Javascript resources that already exist...