|
|
|
|
|
by mclifton
3742 days ago
|
|
Scala.js makes sense when everyone on your team works on every level of your stack - generally smaller teams without any specialization. I'd agree with the other commenters that it makes a lot less sense if you are hiring outside front end devs. You'd probably have a lot less friction if you stick to something more mainstream - either pure Javascript or maybe typescript. Since my project (https://invotes.com) is a one man operation written purely in Scala at this point, I've used Scala.js on the front end with great results. It's nice to be able to cross compile common functionality between the server, frontend, and Android. I haven't run into any blocking issues between the three platforms. It's also pretty straightforward. I hadn't used Scala at all prior to this project, but most everything makes sense (and I don't even have a problem with SBT). The biggest downside is the increase in JS size, but at this point it's not too unexpected to have an overall page size at ~1mb, and at least it's all one minified file once it goes to production. |
|