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 major benefit to Wayland is that it has less overhead since apps talk directly to the desktop. Having desktops implement the protocols instead of relying on a external project means that the user experience is cleaner.
For smaller projects like window managers there are libraries that implement the core protocols. This allows for the minimal window managers Linux traditionally had as an option.
I won’t argue that Wayland has issues with remote desktop. The problem currently is that it has to be implemented as a custom non standardized solution by every desktop. I don’t think that there are any portals for doing session management which is unfortunate.
From a accessibility perspective I believe that has already been addressed.
I also don’t see any reason to try to “market” Linux. Windows 11 is the successor to Windows 10. It isn’t that bad compared to ever other version of Windows.
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.
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.
I think it boils down to trade offs.
The major benefit to Wayland is that it has less overhead since apps talk directly to the desktop. Having desktops implement the protocols instead of relying on a external project means that the user experience is cleaner.
For smaller projects like window managers there are libraries that implement the core protocols. This allows for the minimal window managers Linux traditionally had as an option.
I won’t argue that Wayland has issues with remote desktop. The problem currently is that it has to be implemented as a custom non standardized solution by every desktop. I don’t think that there are any portals for doing session management which is unfortunate.
From a accessibility perspective I believe that has already been addressed.
I also don’t see any reason to try to “market” Linux. Windows 11 is the successor to Windows 10. It isn’t that bad compared to ever other version of Windows.
I guess we will see. Tiling WM on Wayland was, at my last check, totally limited to sway. As a dwm guy Wayland has yet to give me what I need.
Have you tried dwl?
I have not, I wasn’t aware it existed until right now.
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.
“i don’t care about that. Hhit was working and now it’s not” - the users
I’ve been using remote desktop for work daily on wayland (kde) for the last 3 or 4 years… I have no idea what “buggy support” you are refering to