3 ms·
And what's frustrating is this isn't just down to poor execution, it's fundamental to the design, and it was repeatedly pointed out from the start. I'm glad the
by didntcheck 3y ago
And what's frustrating is this isn't just down to poor execution, it's fundamental to the design, and it was repeatedly pointed out from the start. I'm glad there's finally been some acknowledgement of issues predicted around a decade ago, but only because the issues have indeed manifested, making it a rather pyrrhic victory
A "simple" solution to a necessary complex problem is just kicking the can down the road, and essentially asking everyone to invent their own incompatible wheels to fill in the missing bits. On X, there's enough flexibility for me to pick a DE and window manager separately, due to the standard modularization, whereas on Wayland, I have to check the compatibility of a screenshot tool with my desktop environment [1], and whether my DE even works with my graphics card! Everything becomes tightly coupled due to the lack of standards
[1] unlike some I actually do support the move to not let any app read the screen or global KB input, but the interface for those that do should have been part of the Wayland project, not just "not our department!"
- noobermin 3y agoWhat is the solution here, if you don't mind me asking. I feel partial here to X, because it just "works", but as the article this cites, there are real issues to X and this afflicts the upstream developers, whom we need to develop our windowing system in the first place.