• 1 Post
  • 922 Comments
Joined 2 years ago
cake
Cake day: July 29th, 2023

help-circle






  • Do these updates not go through any rigorous testing at all

    Lol no, MSFT infamously dropped their entire Hardware QA team after WIndows 7 and instead relied on the also infamous insider hub to get QA “feedback” from home users instead, leading to the also infamous Windows 8 disaster and slightly less infamous critical CVEs that went unaddressed because MSFT ddidn’t even bother to read the insider hub posts.

    Oh and they didn’t learn anything and kept running with the insider hub well into Windows 10 & 11.








  • Its still lagging is its MRs, like HDR coming in just less than a year ago.

    Valve’s complaint was that even after getting approval from at least 3 DE projects, protocols were not getting merged due to hypothetical discussions and implementation baggage.

    I imagine it all started with them making their gamescope compositor a few years ago and realizing a bunch of stuff was still missing.




  • proper HDR

    Is completly up to each compositor to implement properly. Its still experimental in KDE because afaik theres no proper SDR + HDR tone mapping for mixed apps on the display, like a desktop.

    Valve made their own compositor and cheats the problem by ensuring their client and overlay supports HDR colors + only having to handle the HDR from game output.

    full VRR support

    Not if you have an Nvidia GPU before 2017, and again already a thing in X11.

    no screen tearing and reduced latency

    Again, VRR and wayland’s ingenious solution to this was triple buffering, which is a pure software solution that adds latency making it unsuitable in several cases like this: https://github.com/hyprwm/Hyprland/issues/3373

    The clipboard also works fine

    Welcome to Xwayland clipboard hell: https://github.com/hyprwm/Hyprland/issues/6132

    Its not that Wayland can’t easily fix any of these issues or that the other major improvements you mentioned are not worth it, its that it took Wayland like 13 years to do so.

    Most of this should have been sorted out in the first couple years of development. People were already making fun of Wayland back in the day for pretending to be “decoupled from the graphics hardware” and then deciding on the aforementioned triple buffer.

    Wayland didn’t even merge in HDR support until 9 months ago: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14#note_2777587


  • Fedora (with KDE Plasma) or OpenSUSE tumbleweed (with KDE Plasma)

    Mint is good but its kernel is usually slightly out of date and it still has upstream Ubuntu issues.

    Other Ubuntu downstreams are subpar imo.

    Plus Fedora & OpenSUSE ships with SELinux if you want MAC security support.

    The only downside for Fedora is you have to enable 3rd party software after install and run a couple of commands to swap to full ffmpeg and Nvidia drivers if you have Nvidia hardware. I think OpenSUSE might ship with these enabled but I forgot.


  • mlg@lemmy.worldtoTechnology@lemmy.worldScrew it, I’m installing Linux
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    19
    ·
    25 days ago

    Wayland is responsible for kneecapping linux desktop in so many ways its infuriating, especially since linux basically figured out the golden standard of UX design back in the 2000s with stuff like GNOME 2 and Compiz.

    It’s such an unnecessary burden with progress as slow as ripoff projects like star citizen.

    I hope valve picks up the slack with frog protocols or at least gets PRs merged, because it would be stupid to ship steam machine and then explain to the user that the clipboard doesn’t work yet, even though it used to work perfectly fine in X11.