Remote desktop support is buggy on gnome and nearly non-existant on other DE's, which speaks to how poor a job wayland does at managing functions between DE's, where each individual DE has to build their own solution for basic functions, further fragmenting development efforts.

Then there's accessibility functions, which wayland breaks almost by design by denying apps access to each other. Even something as simple as an on screen keyboard becomes nearly impossible to implement.

Any software thats being pushed to users as the "main" experience, should not break things as common and fundemental as remote desktop or onscreen keyboards. Great way to drive away potential users switching from windows 10.

[–] The_Decryptor@aussie.zone 5 points 1 week ago (1 children)

Then there’s accessibility functions, which wayland breaks almost by design by denying apps access to each other. Even something as simple as an on screen keyboard becomes nearly impossible to implement.

That's a side effect of just dumping everything into X11, once you switch from it you lose all the random kitchen sink warts it grew over the years.

Like an on-screen keyboard shouldn't be fiddling with a display protocol to fake keyboard inputs, it should be using the actual OS input layer to emulate them (So then it'd work with devices that read input directly and not go via X11). Same with accessibility, there's a reason other OSs use separate communication channels with their own protocol.

[–] vrighter@discuss.tchncs.de 2 points 1 week ago

"i don't care about that. Hhit was working and now it's not" - the users

load more comments (12 replies)

load more comments (35 replies)