That's not the problem. The problem is all the heckling for everyone to switch to Wayland, and to make it default. And also pretending that reversing the "mechanism, not policy" wasn't a fundamental change of philosophy and was just "progress".
And to be clear, by "at worst" I meant "this is the least-charitable interpretation".
>Nah, this is an ecosystem maturity problem that is improving rapidly.
TinyWM is 50LOC and wlroots's TinyWL is 900LOC. This hasn't changed. Writing Wayland compositors is a pain in the ass compared to WMs.
Wayland started in 2008 IIRC, so here in 2024 Wayland is 16 years old. It doesn't have teething issues, it just has issues.
Plenty of WM makers have just straight-up said they won't ever port their WM to Wayland (so talking about time and how "X is older" is irrelevant here), because Wayland's opinionation breaks too many things.
>One of the biggest pieces of “jank” replaced is the nonexistent security model.
You mean like how X clients can read keyboard inputs? There's so much FUD around this. /dev/keyboard does that already, you need to sandbox every app anyway - at which point your sandbox should just interdict the X interface. Security is the worst argument. Wayland isn't necessary for security, and for the longest time it's been locking the door and leaving the window open. Portals.
