Will there be a version of compose that can be converted in runtime?That way there can be support for custom UI fetched from remote repositories.It can be good for things like custom popups or A/B testings
Any tips on why Compose functions are structured via
annotation rather than something more common in Kotlin dsl’s
extensions on some context object?
It seems to me that it could make this more extensible and user-friendly than annotations and compiler plugins
I’ve read about it somewhere that devs went out from traditional “build-view-tree -> diff-view-tree -> dispatch-changes” way to improve performance. Are there any studies on how much actual performance gained?
Setting aside the performance question entirely, the decision to use unit functions like this is also a win for the API shape itself. If you call something, it's part of the composition. You can use normal looping and control flow constructs without requiring people to use functional map/filter/etc. as the only option