And it will only support the native targets they s...
# squarelibrariesj
jw
08/05/2022, 5:44 PMAnd it will only support the native targets they support which a few weeks ago seemed like only iOS, unfortunately
l
Landry Norris
08/05/2022, 6:13 PMiOS and native macOS for now.
k
KamilH
08/05/2022, 6:30 PMSounds good as a starter 🙂
j
jw
08/05/2022, 6:50 PMThere's no reason to limit the runtime to so few targets. We build the runtime for another project for all native targets without problem.
l
Landry Norris
08/05/2022, 6:51 PMFor Compose UI, it makes sense. They have to integrate with the platform’s UI libraries, which means adding a new platform is a lot of work. Luckily, this creates a higher level abstraction so libraries using Compose can support all compose targets.
j
jw
08/05/2022, 6:52 PMNo, for Compose UI it makes sense. For Compose it makes no sense.
l
Landry Norris
08/05/2022, 6:52 PMYou’re right. Currently, Compose UI is the primary use for Compose, but hopefully that changes over time.
e
eygraber
08/05/2022, 9:06 PM@jw is this a prioritization issue on their part (i.e. they have no incentive to support them so they won't)?
It's a shame that you called these things out years ago and nothing's happened. Aren't you glad there's now Compose, Compose UI, and Compose for Desktop?
l
Landry Norris
08/05/2022, 9:06 PMIt’s more likely that iOS support for Compose UI is taking up all their time right now.
j
jw
08/05/2022, 9:08 PMAdding native targets to the runtime is exceptionally easy. Like I said, we build and run the Compose runtime's test suite on all targets that coroutines supports.
jw
08/05/2022, 9:09 PMI will try to bring it up to them somewhere