Why Wayland (and XWayland) Won't Solve the Key Problem It Proclaims to be Tackling (the Same Is True for Rust)
Last month: Why the "Wayland People" and "Rust People" Will Lose Hearts and Minds (Same Reasons)
Wayland is far from perfect or elegant:
Wayland is implemented in C.
I've just browsed LWN archives for all of July. On weekdays LWN publishes a list of security fixes (there are also weekly summaries). In the month of July (3 weeks ago far) there have been half a dozen security-related bugfixes in XWayland (different distros) and we remind readers that XWayland is how Wayland People sell Wayland as compatible. Because they're unable to solve very fundamental issues. There are barriers or obstacles they will always fail to leap past.
So what problem is being solved really? Even if everyone moved to a "Wayland session", we'd still have incidents like these.
The problem isn't Wayland per se but the false promises and efforts to force everybody to move to it whilst insulting or demonising everyone who does not (or won't) play along. It's the same problem with Rust. If you want better security, then mature ("old" as in well tested) code and veteran coders are required, not some "shiny" or "new" thing controlled by Microsoft GitHub, i.e. NSA. █