@android_poet Well, exactly. Changing the tech stack just because KMP is the "best" doesn't make any sense unless it brings some real benefits (you name it). But that's just logic, it doesn't make one tool better or worse than the other.
@android_poet The consumer market doesn't demand "tools", it demands "solutions". It's completely up to you how to satisfy that demand as long as you're more efficient than the rest of your competitors. In that sense KMP is at least not worse than the rest of the multiplatform tools.
@jmwilt21@JakubGrzechnik@ArdamirofArda@anothercohen Not so sure. A couple of days ago my Tesla did an emergency break because of a freaking pigeon 3 meters ahead. Now I can't relax when I'm driving. At this point FSD looks scary to me.
@VasiliyZukanov Yes, they do. "Atomic state transition" might not be the best wording, but what I mean is that for the external observer "do stuff" methods immediately cause state transition, without a need in an explicit sync. But again, I'm talking about a state pattern, I don't know your code
@VasiliyZukanov Well, the classic state pattern does not have a sync method (unless that is a private API). Every "do stuff" function causes atomic state transition instead.