What should be addressed in the compose desktop library is the default import behaviour. E.g. by default the desktop library should be material-agnostic, then the developer would import either material or material3. In that way, the "material2" composables wouldn't mix with the 3 if not necessarily needed, effectively avoiding issues where some composables take their appearance from a m3 theme and some others from m2, where the developer forgot to upgrade or mistakenly imported the material 2 composable