"And yet, almost nobody uses it for mainstream frontend development. The reasons are mostly pragmatic. Finding Scala developers is already hard. Convincing a company to build its primary, customer-facing web product with Scala.js means betting on a niche within a niche. That's a bet most businesses won't take. There will always be enthusiasts - but they are the exception. On top of that, many Scala developers (myself included) have limited interest in the traditional frontend ecosystem."
"Scala.js doesn't need to compete with TypeScript and React for customer-facing products. There is a much better and more realistic opportunity: internal tools. Admin panels, back-office dashboards, operational UIs - the kind of software every company needs, but nobody wants to overinvest in. These applications tend to share a few characteristics: Speed of development beats polishEvery hour spent on internal tooling is an hour not spent on the core product. Functionality over aestheticsAs long as the UI is usable and doesn't look terrible, nobody complains."
Scala.js enables backend developers to build web applications using the same language, type system, and mental models they use for server-side code. It is mature, stable, and battle-tested. Mainstream frontend adoption is low because Scala developer supply is limited and companies avoid betting their customer-facing products on a niche technology. Many Scala developers also lack interest in rapid frontend ecosystem churn. A stronger opportunity exists in internal and back-office tools such as admin panels, dashboards, and operational UIs. These applications prioritize development speed and functionality over polish, often get implemented by backend engineers, and tolerate simpler UI workarounds. In that context, Scala.js allows reuse of types, domain logic, and familiar mental models.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]