Scala Test-State VS µTest

It actually been rock-solid for many, many years now! I've built quite a few things with it and introduced it to teams who picked it up very quickly and with no major problems. I've never had any production problems with it EVER and I've been living and breathing it pretty much every day for ages now. It's very, very unit testable (oh! check out Scala Test State if you're interested in really powerful and concise Scala.JS testing) so it's nearly trivial to have to very well tested webapp, including mouse clicks, key presses, whatever you want. Awesome awesome stuff and the Scala.JS team deserve some kind of tech Nobel prize imo. It's been a game changer for me.

Let's clarify some points for folks not so familiar with Scala.

> * Scala minor version are binary incompatible, so maintaining Scala projects is a big pain. Upgrading Spark from Scala 2.11 to Scala 2.12 was a massive undertaking for example.

Scala just chose a strange naming scheme. Other languages would have just increased their major version instead. The scala minor version is increased every few years and not every month or so.

> * Scala has tons of language features and lets people do crazy things in the code.

Actually, that's not true. Or rather: compared to what language?

Scala has surprisingly few language features, but the ones it has are very flexible and powerful. Take Kotlin for example. It has method extensions as a dedicated feature. Scala just has implicits which can be used for method extension.

> * Scalatest is stil used by most projects and is annoying to use, as described here: https://github.com/lihaoyi/utest#why-utest. The overuse of DSLs in Scala is really annoying.

I agree with the overuse of DSLs. Luckily that got much better, but older libraries like scalatest still suffer from that.

> * Li's libs (os-lib, upickle, utest) have clean public interfaces, but most Scala ecosystem libs are hard to use, see the JSON alternatives for examples

I think that just comes from using the library in a non-idiomatic way. In most applications, you will need to use the whole json anyways, and then you use (or can use) circe like that:

    {