We use Scala as well and are very happy with it. We also have a lot of TS, and at this point we are tempted to just switch to using ScalaJS on the frontend as well because of how much better the language is to use. It feels like Scala 3 fixed a lot of issues people had with the language. The IDE tooling isn’t the best, but even then it feels like the IDE tooling for TS breaks all the time once the project is large enough.

> We also have a lot of TS, and at this point we are tempted to just switch to using ScalaJS on the frontend as well because of how much better the language is to use.

I did that and highly recommend it, at least for new projects - not sure that it's worth the effort of porting an existing project, but ScalaJS just works and I found far fewer rough edges than I expected.

How's the tooling story with Scala these days?

I played with it a long time ago and the IDE (eclipse plugin?) was a bit of a mess, sbt was prone to weird issues and lock ups and the compiler was pretty slow.

Very fun language tho!

Some of the folks now work for JetBrains, thus InteliJ is the one with best support.

Then they decided to focus the remaining effort on Scala Metals, which is based on LSP protocol.

In both cases it is alright for Scala 2, there are some rough edges for Scala 3.

The compiler is faster than it was, but not exactly fast. SBT I avoid as much as possible, so can't really speak to that. The eclipse plugin is sadly abandoned, but IntelliJ has pretty good support.

I had this feeling when Kotlin (that took a lot of ideas from Scala)

Intellij tools are great.