3 ms·

No proper screen sharing through any mainstream videoconference application is a killer for work. (0) chromium doesn't support wayland yet, so it is blurry in

No proper screen sharing through any mainstream videoconference application is a killer for work. (0) chromium doesn't support wayland yet, so it is blurry in HiDPI displays with scaling (chromium-dev does, but it has so many bugs it isn't even funny). As a consequence, all electron apps end up blurry... of which there are many. Same applies to all apps that don't support Wayland yet. For example, I spend 90% of my time using Emacs, and it is blurry on Sway if I enable HiDPI scaling. --- So sure. If you don't have a "modern" HiDPI monitor, and if you don't need to screen share often, and if you don't need to use chromium for work, or any App that doesn't support wayland yet, like all electron apps, Emacs, etc., or your work involves ML, or you want to game, or have an nvidia graphics card, which sway does not want to support (as opposed to gnome and kde), and you don't want to buy two GFX cards, or if you have to do screen sharing, or probably another dozen other things that most users need to do occasioanlly, or even every day. Then, and only then, Sway might be for you. But you can also use i3, where all this stuff just works. --- (0) I've seen people creating virtual webcams using OBS studio to capture their screen and share it as their "webcam" in videoconferences, but no mainstream software really supports this "as screen sharing", so the quality is quite bad, in a meeting with 10 people everyone needs to pick the webcam because the apps don't support this huge hack, etc.

pedrocr 6y ago
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 so it's still a work in progress in places but it also has unique upsides from the Xorg experience.
- StillBored 6y ago
  "unique upsides from the Xorg experience" Genuine question, from a users perspective what are they? The couple times I've used it, I ended up going back to xorg because it turned out something didn't work (intel integrated graphics) right. Its sorta become a habit now.
  - pedrocr 6y ago
    The biggest for me is actual tear-free rendering. All the different hacks in Xorg have never worked completely. The other one that people value a lot is HiDPI scaling done "well". Mixed fractional scaling in Xorg doesn't really work and it's finally possible to do it. Although there I actually think it's still a half step and Wayland made the wrong choice in how to implement it. It should have been done client side for more performance and less fuzzyness. There's a chance that will also be fixed in the future. Other than these it's a bunch of small things that are more technical than user-visible. Security is much improved for example. Some performance gains can be had from avoiding copying buffers. Etc.
  - fluffything 6y ago
    HiDPI displays is what I see mentioned the most. But when you then ask if fractional scaling works on Wayland, the answer is "yes, but it doesn't work for any app you actually use". If all you want to do is download a "demo" terminal, and put it in a HiDPI display, and enable fractional scaling, to show it to your friends, then yes, this works. If you want to get some work done on any app (a text editor, web browser, ...). Then its worse than Xorg at the moment.
    - pedrocr 6y ago
      This is false. I can and do set whatever scale factor I want for each screen in sway and all apps are scaled correctly. This includes my browser, my text editor, my terminal, word processor and spreadsheet. There's literally no app I use where I have a problem.
      - fluffything 6y ago
        All apps I use have a problem. Slack, Zoom, Chrome, Emacs, LibreOffice. The only app I use that doesn't have a problem is Alacritty, which is the terminal emulator I kind of have to use to avoid this problem. Other terminal emulators I've tried do have this problem.
        6y ago
- fluffything 6y ago
  > 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?
  - pedrocr 6y ago
    Going one by one: - 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.
sirn 6y ago
FWIW, the thing about HiDPI being blurry is partly design difference between X11 and Wayland, and partly design decision on sway part (to not support this scenario). Having X11 and Wayland applications in HiDPI means having to handle two DPI in a single screen (e.g. sway have to render Xwayland window at 1x, while other windows at 2x). This can be quite tricky since Xwayland's DPI may not always equal to `display DPI * Wayland scale` and while DPI settings in X is global, scale settings in Wayland is per-output. GNOME for instance has HiDPI working for both Xwayland and Wayland windows but with lots of magic going on with the framebuffer. HiDPI for X window in Plasma is still in the works AFAIK. (This is a blocker for me as well.)

pedrocr 6y ago

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 so it's still a work in progress in places but it also has unique upsides from the Xorg experience.

StillBored 6y ago
"unique upsides from the Xorg experience" Genuine question, from a users perspective what are they? The couple times I've used it, I ended up going back to xorg because it turned out something didn't work (intel integrated graphics) right. Its sorta become a habit now.
- pedrocr 6y ago
  The biggest for me is actual tear-free rendering. All the different hacks in Xorg have never worked completely. The other one that people value a lot is HiDPI scaling done "well". Mixed fractional scaling in Xorg doesn't really work and it's finally possible to do it. Although there I actually think it's still a half step and Wayland made the wrong choice in how to implement it. It should have been done client side for more performance and less fuzzyness. There's a chance that will also be fixed in the future. Other than these it's a bunch of small things that are more technical than user-visible. Security is much improved for example. Some performance gains can be had from avoiding copying buffers. Etc.
- fluffything 6y ago
  HiDPI displays is what I see mentioned the most. But when you then ask if fractional scaling works on Wayland, the answer is "yes, but it doesn't work for any app you actually use". If all you want to do is download a "demo" terminal, and put it in a HiDPI display, and enable fractional scaling, to show it to your friends, then yes, this works. If you want to get some work done on any app (a text editor, web browser, ...). Then its worse than Xorg at the moment.
  - pedrocr 6y ago
    This is false. I can and do set whatever scale factor I want for each screen in sway and all apps are scaled correctly. This includes my browser, my text editor, my terminal, word processor and spreadsheet. There's literally no app I use where I have a problem.
    - fluffything 6y ago
      All apps I use have a problem. Slack, Zoom, Chrome, Emacs, LibreOffice. The only app I use that doesn't have a problem is Alacritty, which is the terminal emulator I kind of have to use to avoid this problem. Other terminal emulators I've tried do have this problem.
      - 6y ago
fluffything 6y ago
> 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?
- pedrocr 6y ago
  Going one by one: - 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.

sirn 6y ago

FWIW, the thing about HiDPI being blurry is partly design difference between X11 and Wayland, and partly design decision on sway part (to not support this scenario). Having X11 and Wayland applications in HiDPI means having to handle two DPI in a single screen (e.g. sway have to render Xwayland window at 1x, while other windows at 2x). This can be quite tricky since Xwayland's DPI may not always equal to `display DPI * Wayland scale` and while DPI settings in X is global, scale settings in Wayland is per-output. GNOME for instance has HiDPI working for both Xwayland and Wayland windows but with lots of magic going on with the framebuffer. HiDPI for X window in Plasma is still in the works AFAIK. (This is a blocker for me as well.)