| > All the things you mentioned are already fixed and most have had reasonable workarounds for a while. [...] Some are still working their way through the distros [...] Can you back this up ? Because I can back this up that this is not the case. * Neither Chromium nor Firefox properly support wayland yet and have a lot of bugs. Fedora ships a patched version of Firefox to workaround some of these issues, so does arch, but none of this is properly fixed. Chromium-dev + patches does not handle multiple displays with different resolution (text is in the wrong position, toolboxes are wrong), it is not able to share a full screen (shows up as black), etc. * Emacs does not support Wayland yet. Some users have some patches no enable GTK3 wayland support, but these work badly with Wayland/Sway, not properly recognizing input devices (e.g. Delete key recognized as Backspace is the classic bug for this). Users using these have to remap their keyboards every time they start emacs. * Point us to one Electron app with Wayland support please. Just one. Go ahead. I'll go sit down, and wait, in case you need to wait for any to be released, maybe next year, or the year after that. Whatever the "Year of Wayland" in the Linux desktop will be. * Can you share a screen shot of the Zoom or Webex videoconferencing software (the native packages) on Sway sharing monitors ? If not, don't worry. Can you share a screen shot of using their crappy web versions through any official browser release (unpatched) sharing full monitors through screen sharing? |
- I've been using Firefox as Wayland native for a long time now. It works fine, certainly better than in X. I use the version as shipped by Ubuntu with no changes. Initially there were some bugs but haven't had any that are Wayland specific in a while. Chrome has recently enabled Wayland support in the release builds. I've only briefly tried it in that mode so I don't know what bugs it may have.
- Emacs is X-only because of the way it's built, that will take a while to fix. But XWayland works fine. The blurryness with HiDPI is fixed by a workaround in XWayland. I haven't used it myself because I don't use either emacs or fractional scaling but the solution exists.
- Electron is now getting Wayland support with the new versions but it's not needed to use those apps. I use Microsoft Teams daily in a HiDPI screen even. It works fine under XWayland and even has a setting to change the size of the interface if wanted. Everything but screen sharing works.
- Screen sharing with pipewire exists and works in both Firefox and Chrome, it's still going through the channels to be available in distributions. The first workaround is sharing a tab instead of a screen in Chrome. That has always worked fine and I've used it extensively for presentations. The full workaround is that Chrome under XWayland is also able to share any other XWayland window so it's possible to create a fake output, connect to it using a VNC app running under X and share that app. Complete hack until we get proper pipewire support from Electron apps adopting newer Chromium. Don't know about Zoom and Webex but if those support X sharing the same hack works and if they're native apps they also need a pipewire patch.
If you're happy with your Xorg session then by all means stick with it. Quips about year of the Wayland desktop are actually quite appropriate as they're the same as the complaints about year of the Linux Desktop. For me the year of the Linux Desktop was over 20 years ago, and I've been taking advantage of it ever since. The year of the Wayland Desktop for me was this year, as even after dealing with the rough spots I've gotten quite a bit of value from the transition. If you use different apps or have different requirements you may want to wait more, no one is forcing you to switch. Complaining online that your use cases aren't solved to your satisfaction in open-source projects is a bit much in my opinion.