simon peter (the creator of the AppImage standalone package format) recently I make a post on GitHub in which basically called for a boycott of Wayland "Since it breaks everything."
One of the key problems, in his opinion, is that with Wayland many applications are corrupted and the developers of Wayland hope that the authors of the application will fix everything themselves.
In the post message share the next
“Wayland doesn't fix any problem I have, but it breaks almost every application I need. And they remain inoperable because the people of Wayland seem to only care about GNOME and spit on everyone else. " DO NOT INSTALL WAYLAND! Don't let Wayland destroy everything so others don't have to troubleshoot later. Or promote more specific Red Hat / GNOME components (glib, Portals, Pipewire) as required dependencies! «
Inside the post, share some of the following examples, on application types that "break with Wayland":
Wayland breaks screen recording apps
- Wayland does not support screen recording applications. For example:
SimpleScreenRecorder: the author will not support Wayland until there is a standardized interface that is not linked to GNOME. Broken since Jan 24, 2016, no resolution ("I assume they use a non-standard GNOME interface for this") - OBS study. At the same time, there is a GNOME specific plugin that allows you to use OBS Studio with Wayland, but only when using gnome-shell. Yes OK an active OBS Studio contributor notes that the X11 Screenshot API is very close to worst possible, the screenshot situation is a good example of how (GNOME) Wayland regressed to something more difficult to use than X11 and perhaps technically inferior to it.
Broken since at least March 7, 2020. ("Wayland is not supported at this time", "There really isn't anything that can be easily changed. Wayland does not provide Capture API") - https://github.com/mhsabbagh/green-recorder
- https://github.com/vkohaupt/vokoscreenNG/issues/51 Rsince at least 7 Mar 2020 ( "Now I have decided that there will be no Wayland support for the moment, there is no budget for this, we will see how it looks in a year or two ..") - This is the key problem. Wayland breaks everything and then hopes that others will fix the problems he caused on their own.
Wayland breaks screen sharing apps
- Wayland does not support screen sharing applications. For example, jitsi-meet. At the same time, for example, in Fedora 32 it is possible to share the screen in wayland sessions (using xdg-desktop-portal, which uses Pipewire).
- https://github.com/jitsi/jitsi-meet/issues/2350 broken since January 3, 2018
- https://github.com/jitsi/jitsi-meet/issues/6389 broken since January 24, 2016 ("Closing because there is nothing we can do from the Jitsi Meet side") . Wayland breaks things and leaves app developers helpless and unable to fix the flaw, even if they wanted to.
- https://github.com/flathub/us.zoom.Zoom/issues/22 Zoom broken since at least January 4, 2019. ("Can't start sharing, we only support wayland on GNOME with Ubuntu (17, 18), Fedora (25-29), Debian 9, openSUSE Leap 15, Arch Linux"). Nothing is known about non-GNOME!
In addition to it it also mentions that:
- Wayland is incompatible with the GNOME global menus.
- Wayland is incompatible with the global menus of the KDE platform plugin.
- Wayland does not support Qt-based global menus.
- Wayland is incompatible with the AppImage packages provided without a dedicated Qt plugin.
Finally the author of the initiative will be happy to add other existing examples to his list if more people join the initiative and even to prove that Wayland is not viable.
What is true and that most of the Linux community knows, is that Wayland still has many problems with screen recording applications (screen recorder), also with remote access applications, since there are still several problems to solve with the handling of the keyboard and mouse (a quite old problem and that I personally do not know if it has already been worked to solve, since as I mentioned it is a problem that had been dragging on).
And what do you think about it?
Wayland is broken with everything, Xorg is more dead and repaired than anything.
Complicated this situation for Linux.
Wow, thanks for making me laugh. I did not know that the creator of Appimage was a snowflake.
Safety matters and that's why Wayland was born. X.Org is dead due to lack of maintenance. It would be best to provide patches to use Wayland by asking the user for permission to access the resources.
On the other hand, AppImage is not necessary, nowadays there are packers for deb, rpm and others. The security of what is installed matters. Packages signed by the distribution. It is another way of understanding things, where security is important about what you are going to install. AppImage also causes duplication and additional memory consumption. How would a boycott of AppImage feel for these reasons?
use mir from ubuntu…. or wait for the community did not give the support what a shame