Currently, the packages name are in `androidx.comp...
# compose-desktopt
theapache64
02/04/2021, 6:52 PMCurrently, the packages name are in
androidx.compose.*a
Ali Albaali
02/04/2021, 7:00 PMi
ian.shaun.thomas
02/04/2021, 7:02 PMI think Jake Wharton's article on naming comes to mind here as well and has a lot of community support. This seems highly related and probably worth discussing again in whatever format those discussions happen.
r
romainguy
02/04/2021, 7:02 PMWho looks at imports? 😛
🧌 5
✋ 11
i
ian.shaun.thomas
02/04/2021, 7:02 PM✋
a
Ali Albaali
02/04/2021, 7:03 PMEverytime the IDE doesn't import getValue and setValue for mutableStateOf 🧐
r
romainguy
02/04/2021, 7:04 PMThis is a discussion we (Google/Android Compose team) have had several times and we decided to keep those package names
😭 5
🤦♂️ 2
😢 2
g
gbaldeck
02/04/2021, 7:43 PMI dont know you guys requirements, but compose.framework.* for the interfaces and other multiplatform code, then compose.android.* , compose.desktop.* , compose.web.* , compose.ios.* (ios maybe someday 🙂 ), for the implementations make a lot of sense to me
👍 15
b
Ben Woodworth
02/04/2021, 11:19 PM@romainguy Is it just that it's too inconvenient to change at this point? I'm pretty curious what the takeaways from the discussions were
t
theapache64
02/05/2021, 4:37 AMI agree with @gbaldeck. If you guys wanted to have the same package name across all platforms, should have gone with something generic. like,
com.compose.*👎 1
💯 1
g
gildor
02/05/2021, 5:39 AMcompose.com is not related to jetpack compose %) just
compose💯 2
t
theapache64
02/05/2021, 1:25 PM@gildor i didnt mean exactly
com.compose.*i
ian.shaun.thomas
02/06/2021, 12:15 AMSo why not share the reasoning of keeping the naming tilted towards maximum confusion?
l
louiscad
02/13/2021, 1:02 AMJetBrains CEO is sad about that decision you (Google/Android Compose team) made unilateraly (and is not the only one it seems).
But… it's not too late to change to
compose.*💯 1
☝️ 1
i
ian.shaun.thomas
02/13/2021, 1:04 AMSeriously please change it or at minimum pretend this is open source and convey critical decisions and their reasoning.
a
Ali Albaali
02/13/2021, 1:19 AMI think a lot of people agree on this. Taking the community's opinion into consideration is not a bad idea at all, and I think right now is the perfect time for such change, because Compose is only going to get bigger.
l
louiscad
02/13/2021, 5:22 PMDirectly pasting the link of the petition for people in this thread: https://www.change.org/p/google-drop-androidx-from-jetpack-compose-package-name-for-multiplatform-before-1-0-release
g
gildor
02/14/2021, 12:18 AMI understand that decision from Compose team (or Google in general), after all they invested vast majority of time/money/human resources. So it's their decision. Keep it in the same package as other JetPack libaries makes sense on some level
But I don't think that changing package name to compose.android would somehow affect adoption on android (it will be the main UI framework, after all) , but it indeed makes it more frustrating and confusing to use on other platfroms and maybe not critically, but still may hard adoption on other platforms.
Also in terms of usability, having
compose.${platform}3 Views