The interface exists. It’s up to zoom to support it. Why are you under the impression there is a technical issue? THERE IS NONE.
It’s up to Zoom to support the aforementioned interface.
Wayland’s display handling in this manner is for security, the user will be shown a permission request dialogue to let the app access the screen only if you permit it, it’s also disallowed from accessing anything except what you’ve given it permission to. This is not even a new concept, just not doable under X.
It’s also possible to create the lawless model of X under Wayland through a protocol if you desire to make one, but it makes little sense to throw away this better model just for the sake of some shitty proprietary apps who don’t care for Linux anyways
Again, none of that is a failure of Wayland, it’s a failure of Zoom to run on Wayland. One day, and this is in the next 5 years, Wayland-only apps will refuse to run on X.Org and the situation will be reversed.
You can share screen perfectly fine under Wayland. Many apps use it fine, and even in case of Discord if you use it with a browser it’s doable.
No Wayland dev can fix an issue that originates from lack of app support. There has been many Wayland issues through the years and trust me, I know, but how do you expect them to fix Zoom? Acquire the company and take it behind the shed?
XOrg is designed so a central server (mainframe) sends and receives data from smaller terminals, and that not only includes a heap of devices that haven’t been in use since the 90s it also has a ton of features that nobody uses. (See: X native fonts, X native widgets, X driver model…)
X’s way of handling events and sending draws to clients as such is somewhat convoluted. Once you start to really dig into it, it’s amazing how much people managed to stack on top of it until today.
Besides, modern day X over Network is a somewhat niche and possibly broken function
This also depends on the desktop you use. GNOME is by far the most stable [In My Experience], and KDE spent the whole 5.x series getting their Wayland support into shape. What you’re describing could be XWayland failures (games don’t run on Wayland lol) and desktop environment bugs.
Depending on how long ago you’re talking about, your hardware, and your desktop of choice, things might’ve been improved a lot since the last time you used a Wayland session.
After finally realizing nobody is interested in EGLstreams, Nvidia seems to be on track to make their drivers less of a disaster for Wayland support, so thankfully it is bound to become better
I just want you to know, this isn’t a failure on anything other than Nvidia trying to force their own crap on everyone and failing
Sounds like a heap of crap. X.Org developers moved to Wayland, they were the ones who made it happen. Now, I wonder where this dude with his XOrg Forks and PhD and shit was during all that 15 years it took to conceptualize wayland.
You all need a lesson in taking everything people say, including and most importantly their qualifications with a huge grain of salt.
Wayland has been working perfectly for years now. Many of the supposedly “impossible to implement” functions of the old hunk of junk Xorg were either found to be bogus anyways or have been made available on Wayland.
Sincerely– Someone who’s been using wayland since 2016
Which no, haven’t gone away as the technology advanced as many people would like to believe, we’re still using displays and networking and keyboards and mice.
lmfao Wayland is already ready for over 90% of use cases. Hell, GNOME has been wayland-default since twenty-fucking-sixteen if I remember my dates right. You’re overestimating the value X.Org provides.