3 ms·

That matches my experience as well. I'll do a fresh distro install and not notice at first if it defaults to Wayland, then I'll run into something. It might be

That matches my experience as well. I'll do a fresh distro install and not notice at first if it defaults to Wayland, then I'll run into something. It might be crashe or app compatibility (I had a game on Wine once that crashed on Wayland but not X11), but it drives me to switch things over to X11.

ugjka 5y ago
Wine doesn't work on Wayland period. You need wine-wayland and that only does games not regular windows programs
nextos 5y ago
Also all tiling window managers will need to be rewritten from scratch basically as Wayland's architecture is very different, which sucks.
- CyberShadow 5y ago
  It's worse than that. Window managers simply cannot exist in Wayland, because the compositor is the only actor which can also do window management. This coupling is one of the biggest design faults of Wayland. The platform-specific functionality is no longer encapsulated in a stand-alone piece of software - the compositor now must do everything, because Wayland trusts only it to do anything privileged. This leads to less choice and more restrictions. If you wanted to get X11 running on e.g. your phone, you would get the Xorg server Android app, then run the window manager you want, then run the applications you want. This is not possible in Wayland: there would need to be one per-platform app per compositor / window manager, so you would need e.g. Weston for Linux, Weston for Android, Weston for iOS, sway for Linux, sway for Android, sway for iOS, ...
  - porkloin 5y ago
    For this exact reason I think we're going to see a lot more development of DE-specific tiling window management solutions, like Pop Shell, PaperWM, Material Shell, etc., are doing for Gnome. They all just leverage the Gnome Shell extension system, but are inextricably dependent on Gnome.

3 ms·

That matches my experience as well. I'll do a fresh distro install and not notice at first if it defaults to Wayland, then I'll run into something. It might be

by mmcdermott 5y ago

ugjka 5y ago
Wine doesn't work on Wayland period. You need wine-wayland and that only does games not regular windows programs
nextos 5y ago
Also all tiling window managers will need to be rewritten from scratch basically as Wayland's architecture is very different, which sucks.
- CyberShadow 5y ago
  It's worse than that. Window managers simply cannot exist in Wayland, because the compositor is the only actor which can also do window management. This coupling is one of the biggest design faults of Wayland. The platform-specific functionality is no longer encapsulated in a stand-alone piece of software - the compositor now must do everything, because Wayland trusts only it to do anything privileged. This leads to less choice and more restrictions. If you wanted to get X11 running on e.g. your phone, you would get the Xorg server Android app, then run the window manager you want, then run the applications you want. This is not possible in Wayland: there would need to be one per-platform app per compositor / window manager, so you would need e.g. Weston for Linux, Weston for Android, Weston for iOS, sway for Linux, sway for Android, sway for iOS, ...
  - porkloin 5y ago
    For this exact reason I think we're going to see a lot more development of DE-specific tiling window management solutions, like Pop Shell, PaperWM, Material Shell, etc., are doing for Gnome. They all just leverage the Gnome Shell extension system, but are inextricably dependent on Gnome.