kyo VS tyrian

Indeed - I do not think it is a coincidence that a lot of production experiments in effect systems are happening in Scala right now - the language is very flexible to conduct them. https://github.com/getkyo/kyo in particular looks interesting as it explores a different space where the monadic nature is less exposed to the end user.

Now in scala we have direct mode transformers: dotty-cps-async [https://github.com/rssh/dotty-cps-async] with cps-async-connect [https://github.com/rssh/cps-async-connect ] supports all well-knowm monad stacks, for ZIO also exists ZIO-direct [https://github.com/zio/zio-direct ] , for IO - cats-effect-cps [https://github.com/typelevel/cats-effect-cps ], for kyo [https://github.com/fwbrasil/kyo ] - kyo-direct.

Thanks! I'm not sure I understand your use case but it's possible to handle effects even if they aren't present in the computation. An example of that is KyoApp's run method. It handles several effects even thought the application might not use them:

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.