Did you just invent a non-existent core Wayland developer and attack them for things they didn't say? I am all up for shitting on modern software stacks and praise the Unix philosophy, but I am really turned off by posts trying to make this a question about gender identity and generation, as if that has anything to do with it. Old cis-dudes come up with bad software architectures too.
Sorry, but it is kind of a generational thing. If you grew up in an environment where one set of assumptions always held, you are more likely to think that these assumptions are universals and just not even bother with the possibility that they might not be the case. This goes double if you're young; even bright young devs often have not had the breadth or depth of experience to consider that that crusty old protocol they're trying to get rid of due to "legacy cruft" is the way it is for a reason, one which is still reflected in the use cases of real users working today. This has direct bearing on the Wayland situation: one of the reasons why Wayland is having trouble getting traction against X11 is because the Wayland devs have lost sight of the fact that Wayland is designed to solve one set of problems and X11 another.
And real Wayland developers have made the exact argument I attributed to my fictional one, just with fewer anime emoticons (and "watch this talk by Daniel Stone" as a final mic drop).
Did you just invent a non-existent core Wayland developer and attack them for things they didn't say? I am all up for shitting on modern software stacks and praise the Unix philosophy, but I am really turned off by posts trying to make this a question about gender identity and generation, as if that has anything to do with it. Old cis-dudes come up with bad software architectures too.
Sorry, but it is kind of a generational thing. If you grew up in an environment where one set of assumptions always held, you are more likely to think that these assumptions are universals and just not even bother with the possibility that they might not be the case. This goes double if you're young; even bright young devs often have not had the breadth or depth of experience to consider that that crusty old protocol they're trying to get rid of due to "legacy cruft" is the way it is for a reason, one which is still reflected in the use cases of real users working today. This has direct bearing on the Wayland situation: one of the reasons why Wayland is having trouble getting traction against X11 is because the Wayland devs have lost sight of the fact that Wayland is designed to solve one set of problems and X11 another.
And real Wayland developers have made the exact argument I attributed to my fictional one, just with fewer anime emoticons (and "watch this talk by Daniel Stone" as a final mic drop).
Kristian Høgsberg who developed Wayland was in the beginning of 30s when it was first released 17 years ago. Stop this nonsense.