I’m downloading compose-multiplatform-core and syn...
# compose-ios
a
I’m downloading compose-multiplatform-core and syncing it… I’m thankful for this M1 Max chip, I couldn’t imagine how long it would take on my work intel mac…
s
M1 Max just adds more graphic power. I found little difference in speed improvements going from regular M1 to M1 Pro. But yes, M1 is awesome.
a
Yes, it’s quite a big thing.
a
I also do graphic work alongside my normal dev work 🙂
Out of curiosity, does the JetBrains team follow the onboarding step to work on the project? I've wrangled AOSP plenty before, but never had a need to touch frameworks/support. I might be overthinking working with the project given I'm not using it inside AOSP 😅
a
I followed the readme
a
Yeah, I might have to nuke the directory, and start off running studiow in the compose project mode
Did you have to download a bunch of prebuilts?
a
I think most of the team is using IDEA (with the Android plugin disabled). Not Android Studio
a
Ah, that would make sense, I switched from IDEA Ultimate a while back to AS because of the agp tooling support. This is good to know
Finally getting back to it, have you seen anything such as this when building compose sources?
s
Looks like a dependency issue where something is not available for the platform right now. That can happen if someone missed to upload certain artifacts. It get this from time to time, but I don't know about this particular case. In general I try to reduce my dependencies to a minimum to avoid such problems. I don't use any dependency injection framework or navigation framework as I really feel no need for those. Of course I have proper dependency injection and navigation, but not with a framework. The less dependencies, the less issues of those kinds, if you ask me.
a
In this case, this is the AndroidX project which has both AOSP and gradle tooling, not my project!
I can't touch the config, really. Not like a personal project or work project where it wouldn't happen under my control 😅