I feel like there’s also the point that on Mac OS a lot of stuff “just works” because everything else just doesn’t work at all. I have a number of things that just aren’t going to work at all on Mac. Linux is obviously much more permissive, which leads to a lot more kinda working stuff that just wouldn’t work at all on Mac.
The compositors are the ones doing a lot of the protocol development. They want to have WIP versions so they can see what issues crop up, they’ve been making versions all doing. Now, I agree that it is slowing things down, but it’s more of just an additional thing that needs to get done, not so much a chicken and egg problem.
Wine and Proton have actually put a ton of work into Wayland support, it’s very far along. I wouldn’t be surprised for Proton to have a native Wayland version soon.
Also XWayland has many limitations as X11 does.
If an app has only ever supported X11, then it probably doesn’t care about those limitations (the apps that do care probably already have a Wayland version). And if an app doesn’t care about the extra stuff Wayland has to offer, then there’s not really a reason to add the extra support burden of Wayland. As long as they work fine in XWayland, I think a lot of apps won’t switch over until X11 support starts dropping from their toolkit, and they’ll just go straight to Wayland-only.
Programming languages is way too broad a category. There’s a lot of variation in both power and difficulty.
I’m pretty sure Linux still uses Unix-style permissions in NTFS, which causes issues when Windows tries to use its own permission system on the same partition.