They are mission critical must-haves for day one, otherwise people are going to fall back to windows or X11 desktops that didn’t have these obnoxious limitations. This is not optional, and it isn’t acceptable to suggest these features may be available in the future as a justification for an incomplete deployment today. My wife and kids who are not in tech rely on screen sharing teleconferencing. I just tested my screen sharing applications and they all produce black screens under wayland □ But the thing is it’s still not working today. While I find it unfortunate, I can live with an inferior design as long as it does in fact work. But most users don’t care how it works, just that it works. Shifting functionality into compositors will probably result in a patchwork of support depending on what desktop software you are running, which is lousy. Honestly they’re “close”, but they need to do the rest… Yeah, it gets frustrating when devs don’t have respect for their users’ needs. Leaving all the functionality up to the compositors is pretty stupid, and having a generic API for such things is rather useful… This is a poor design IMHO.Īlso hate the fact the Xorg devs are doing this as most have switched to developing Wayland before it is quite as capable. I absolutely hate that these basic features are going to be broken/unimplemented/incompatible depending on which compositor one is using for their desktop. If we need a security mechanism to lock down the privileges, that’s fine, but at least then we’ll get a standard solution that works everywhere. What if I want to use VLC to stream my desktop? Now I have to petition to add a VLC capture protocol to the compositor? Hogwash! Obviously it makes more sense to have one generic API for all applications to use. I don’t want VNC/RDP to be hard coded into the compositor. The refusal to support a standard capture API for purely dogmatic reasons leads to more bloat and cruft downstream. ![]() IMHO we’re looking at poor designs steming from wayland’s limitations. There are proposals to hard code support for RDP & VNC into the compositors themselves, ![]() Some protocols which are relevant to VNC servers that have not been agreed upon between different compositors are: Consequently every single compositor needs to implement the missing functionality, which doesn’t offer any greater security and creates a ton of new portability issues… Progress has been very slow for things like vnc because unfortunately wayland refuses to add generic support for screen grabbing, even under security privileges. I am on board as soon as I see them address these bugs & limitations, but if their attitude is “no you can’t do that, we don’t allow it” because their own justifications are more important than our needs, sorry but that’s lazy and the community deserves better. There are tools and capabilities I need to do my work that, so far, don’t work with wayland. IMHO a big problem with the wayland project is that they haven’t been pragmatic with regards to use cases. I’d be happy to use it once they’ve fixed wayland’s limitations. My laptop already runs GNOME for this very reason. GNOME can be made usable with extensive use of extensions, and I’m seriously considering switching to it once the NVIDIA situation is sorted. Second, my desktop environment of choice, Cinnamon, does not support Wayland and has no support coming in the pipeline, which is really disappointing. ![]() There’s still two major blockers, though – first, NVIDIA support is problematic, at best, so my main computer will remain on X until NVIDIA gets its act together. I try to use Wayland wherever possible, since the performance gains and battery life improvements are just too good to ignore. Ubuntu with GNOME Shell on Wayland has been available as a non-default choice but the hope is now in 2021 they are ready to comfortably switch to Wayland. Ubuntu is going to be trying to switch over to using Wayland by default for the current Ubuntu 21.04 cycle to allow sufficient time for widespread testing and evaluation ahead of next year’s Ubuntu 22.04 LTS release.Ĭanonical engineer Sebastien Bacher announced today they will be trying again for Ubuntu 21.04 to enable Wayland by default, four years after they originally tried but reverted back to using GNOME on X.Org for Ubuntu 18.04 LTS and since that point.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |