that’s the thing… wayland has repeatedly said they will not reach feature parity. So from the word “until” onwards cad be deleted, back to the older comment

you mean 365 cloud pc?

“these new cars have a teeny tiny fuel tank with a tiny range! They used to have a bigger tank!”

“Drive an old car”

In this case the new car is objectively inferior, and I can’t buy a new old car anymore.

When something complains about very real problems due to missing functionality, the proper answer isn’t “fuck you, use the old stuff, or stop yearning for the functionality that te intentionally crippled”

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.

well that’s the problem. “I don’t use it therefore it must be a bad idea”

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

it will be refused in the name of security. Which is notreally a good argument. “it rather involved being on the other side of that airtight hatchway” type of thing

I am not better served. I am now in the quite new position where I’d have to rewrite some of my own personal software if i simply just decided to change DE

missing feature that used to be there but has been removed in the name of protecting me from myself, is an inability to customize.

we eat horse (infrequently) where I’m from. If prepared properly it’s delicious