• 0 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle


  • AMDIsOurLord@lemmy.mltoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    11 months ago

    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



  • X11 world is just really as bad. It’s just so that Wayland is new and X.Org hacks are so normalized it doesn’t register for people how much work you need to put into X to make it work.

    Each compositor is tasked with coming up with solutions for all parts of the user experience (hence the last point) and thus anyone who wants to experiment with making their own WM now has to worry about a billion things that wouldn’t have had to deal with in X11

    Well, you would be disappointed to know that it’s somewhat the same fuckery under XOrg as every usable compositor and window manager needs to carry fixes, hacks, and hardcoded workaround for edge cases in X or features that are unsupported today. If you use a Wayland library like you use X libraries it’s not that much harder to make a simple Wayland compositor.

    This is one of the most cited “wayland issues” and it’s IMO completely and utterly wrong. Go look at how convoluted existing XOrg codebases (mutter, metacity, compton, compiz, etc.) are. It’s only “simple” if you wish to draw a rectangle upon the screen ( and even then, wlroots exist)


  • AMDIsOurLord@lemmy.mltoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    arrow-up
    16
    arrow-down
    4
    ·
    11 months ago

    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


  • AMDIsOurLord@lemmy.mltoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    11 months ago

    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.




  • AMDIsOurLord@lemmy.mltoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    arrow-up
    31
    arrow-down
    2
    ·
    11 months ago

    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


  • AMDIsOurLord@lemmy.mltoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    arrow-up
    64
    arrow-down
    15
    ·
    11 months ago

    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