[lmm]

> I'm not the person you ask, but we use fullstack Typescript in our dev department. We're a weird mix of a green energy company and an investment bank, so inhouse development is very small-scale, and this means you share resources. Using one language for everything helps with this, since the one person who is really good at React can take a vacation or a sickday without being glued to a laptop since everyone else can also work on the front-end even though it's not their daily thing (and vice versa). More than that though it lets us do things like code reviews, troubleshoot solutions and generally work together really well, even though we're working on very different projects. It also lets us build libraries that can be used for everything.

We do this the other way around, by using Scala.js so we can use Scala on the frontend as well as the backend. It's very nice.

[RussianCow]

> We do this the other way around, by using Scala.js so we can use Scala on the frontend as well as the backend.

I've wondered about this approach for a while, but have yet to actually try it in any meaningful context. Do you use a framework like React via Scala.js, or are you doing something different?

[lmm]

Yeah it's React and some component library etc.. Library interop is pretty good if the library has type information available, and most of them do these days.