KEEP VS compose-jb

Btw. unsigned types are partially stable now in Kotlin 1.5: https://github.com/Kotlin/KEEP/blob/master/proposals/unsigned-types.md

It will be easier with Context receivers, those are not available yet

If you like the idea of CoroutineScope, CoroutineContext, suspend, you will like the Kotlin Coroutines Design proposal https://github.com/Kotlin/KEEP/blob/master/proposals/coroutines.md

I base my opinions on things that I've read from Mr. Elizarov and from the value classes KEEP: https://github.com/Kotlin/KEEP/blob/master/notes/value-classes.md

Be sure to read the full documentation and how value classes in Kotlin relate to Java’s upcoming Project Valhalla.

https://github.com/Kotlin/KEEP/issues/259 I'm guessing in 1.7 (or by the pace features are currently getting released, 1.17...) it will get an experimental release.

The value classes KEEP itself even raises the point that even once Valhalla is released, its adoption won't be universal at first, and that limiting a major feature like value classes to a specific version of the JVM, or a specific target, doesn't make sense.

Release notes

In the next 6-12 months, I think this will be more possible. Kotlin took Android's new UI framework, Jetpack Compose, and is making it multiplatform. https://github.com/JetBrains/compose-jb

I tried binding my protos into a sourceset of the common module but couldn't get it working.

Currently v1.0.0beta5, the best about it: It's multiplatform (macOS, Linux, Windows) and Web. https://github.com/jetbrains/compose-jb

I will say on the topic of multiplatform, rxjava isn't directly supported. However there is a multiplatform Rx library called reaktive which has way better testing support compared to coroutines at the moment. although if multiplatform is something you're interested in doing I would start the project off rather than do it later to save time in the long run. If you're interested, the mpp Todo sample is a good example demonstrating a lot of everything.