regex VS tyrian

https://github.com/elm/regex/commits/1.0.0/

So it seems like by the time of the official release you could have replaced your five lines with `Regex.fromString`.

But the missing Intl API is definitely a huge pain, and I understand that you were switching away if you needed it extensively. Or expected to want other sync APIs wrapped.

A common way to solve something like this is with proxy objects like in https://github.com/anmolitor/intl-proxy but it does not give access to every feature in a nice way.

I went the route of least resistance and built the Elm compiler without the Kernel code check. But in the past few years I hardly needed that anymore.

If you want to try TEA, but not Elm I reccomend Scala.js with Tyrian[1]. Scala.js is a wonderful, mature project and Tyrian gives you the elm architecture in a very pragmatic way.

[1]: https://tyrian.indigoengine.io/

Have you looked at Laminar and Tyrian? Especially Tyrian seems to be close to what you're looking for.

What I wrote is obviously based on my experience as backend and data engineer. I'm so happy to see an adoption on the Frontend side (with things like Tyrian or OutWatch) and would be even happier if there was a clean path to Android. Out of curiosity, what do you find appealing in Scala, compared to e.g. Kotlin?

Documentation can be found at https://indigoengine.io/ and https://tyrian.indigoengine.io/.

Yes, I have. It didn't work out. There are quite neat libs like Tyrian, but they lack any ecosystem and I struggled to integrate it with pure JS libs - yet our app has a lot of very common components/widgets that we're really hesitating to write ourselves.