see that’s the problem. Everyone’s first response is that it’s a niche problem. For every complaint. So what? It’s a new problem is the point, however niche.
Btw, this is not a niche problem. Some big projects have explicitly said they have had this very problem
Let me rephrase that: it sounds like a niche problem to have for an end user. It also doesn’t sound like a fair complaint, because no long-term replacement to X was ever going to be drop-in the way you seem to expect.
I am not referring to it being a drop-in replacement. I’m referring to the fact that there are multiple supposedly-interoperable-but-not-really non-drop-in replacements is the problem. And it does affect the end user if devs find it difficult to adopt (as many do).
Wayland is designed for ease of development for wayland designers. “We’re just a protocol, the coding is left to anyone else” is the easiest way to write code. Because they decided not to write any at all.
see that’s the problem. Everyone’s first response is that it’s a niche problem. For every complaint. So what? It’s a new problem is the point, however niche.
Btw, this is not a niche problem. Some big projects have explicitly said they have had this very problem
Let me rephrase that: it sounds like a niche problem to have for an end user. It also doesn’t sound like a fair complaint, because no long-term replacement to X was ever going to be drop-in the way you seem to expect.
I am not referring to it being a drop-in replacement. I’m referring to the fact that there are multiple supposedly-interoperable-but-not-really non-drop-in replacements is the problem. And it does affect the end user if devs find it difficult to adopt (as many do).
Wayland is designed for ease of development for wayland designers. “We’re just a protocol, the coding is left to anyone else” is the easiest way to write code. Because they decided not to write any at all.