It won't be replacing XOrg anytime soon, because XOrg is a walking example of "worse is better". Yes, it's ancient, bizarre in some ways, cluttered with feature

It won't be replacing XOrg anytime soon, because XOrg is a walking example of "worse is better". Yes, it's ancient, bizarre in some ways, cluttered with feature bloat and a security nightmare. Nobody denies that. The problem is that said feature bloat is also exactly what makes it attractive to desktop users. I'm not saying that Wayland has no use; it can reliably cover ~90% of all computer tasks and if you're just setting up some sort of kiosk/server with one application, I think it's hard to not pick Wayland since you can just grab a thin renderer and avoid all the extra crap that comes with XOrg. But for desktop, the weird/random things XOrg allows you to do are what makes it the undisputed king to this date. It's not what's best that wins. It's that what covers the widest amount of usecases that does, regardless of any amount of bizarre rituals that you need to do to get it working (and only if you have feature parity does less weird rituals take over in priority). Wayland already lost that race before it even started since feature parity with XOrg is a non-goal. Other examples of this concept in action: Any old-school Microsoft project (really, just all of MS Office), the entire HTTP frontend stack, SQL, PDF.