Honestly, most people shouldn't even much have to know what Wayland is, and the fact that we're even talking about it is a testament to how badly it was done.
It's the thing that makes graphics on the screen, i.e. why you're not looking at a terminal. For some reason, the decision was made to drastically revamp it in such a way that trying to switch caused a lot of problems. This is like a TEN YEAR OLD deal.
These days it’s pretty much done and finished. Xwayland works fairly well to the point you almost couldn’t tell.
The only issue with wayland usage currently is apps in the xwayland compatibility layer are lacking the new features wayland adds like dpi scaling across screens.
I’m very happy that wayland + pipewire + flatpak now gives us basic security practices like apps having to ask permission to record the mic/screen/webcam vs the state of things in X where being able to draw a window also grants full access to everything.
Mostly fail to see the value in the specific thing you're saying; essentially this is the sort of thing that e.g. free/open source ought to take care of regardless.
As in, this is "taken care of" when you agree to install the application; is there any serious reason to believe that security against an "installed application" from a repo benefits from this rather fine grained permission as opposed to what is already in place?
And of course the real issue is usually just "the web browser" which, hey, all bets are off.
It's the thing that makes graphics on the screen, i.e. why you're not looking at a terminal. For some reason, the decision was made to drastically revamp it in such a way that trying to switch caused a lot of problems. This is like a TEN YEAR OLD deal.