in other words, right now everything is running in a single threaded fashion, but it likely will not stay that way, and things like @Model and @Composable have been designed intentionally to support some different threading strategies, but we haven’t been able to test them out yet due to some limitations of the IR kotlin compiler until recently

we’ll talk more about threading strategies once we have a better picture of what works and what doesn’t, since we haven’t experimented enough yet

performance is really important to us, but a lot of things on the compiler side were really about getting things “working” and “correct” first, so that the broader team could iterate on making the toolkit. We are starting to be able to implement some of the optimizations we have been planning for quite some time, and reap the benefit. there is still a lot of low hanging fruit

we have a lot of benchmarks that we are tracking, and will be adding more, but where we are right now is definitely a lot slower than where (i think) we will end up

Also is there something like a

coroutine

effect?

With regards to coroutine effects, not yet, but we plan to add them. The biggest issue is that the IR has not had any support for coroutines until very recently, and Compose depends on the new IR backend, which prevents us from using coroutines. We look forward being able to build APIs that use coroutines very soon.