• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle








  • If you want a preview of an uncaring and anti-consumer Valve, look no further than the company’s efforts on Mac.

    Valve never updated any of its earlier games to run in 64-bit mode… Apple dropped support for 32-bit applications in 2019

    Funny enough, the only platform with a 64-bit Steam client is Mac.

    I don’t disagree with concerns about monopoly, but the author’s key example is Macs. And from the example, it sounds to me like Apple disregards backwards compatibility (dropping 32-bit support, moving to ARM chips) and Valve isn’t investing to keep up. Meanwhile, Windows has a heavy backwards-compatibility focus, and Linux isn’t too bad either, so no wonder they still get Valve’s attention. So who is being “anti-consumer” in this example, Valve or Apple?







  • randy@lemmy.catoLinux@lemmy.mlX11 vs Wayland
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    In your situation, I would say to stick with X11. I’m still using X11 for gaming, but Wayland for most other things. Maybe try Wayland again in a few years. And when it’s time to buy new hardware, maybe avoid Nvidia.

    If you want to have another go at getting it working, check out what the Arch wiki says for KDE:

    If you are an NVIDIA user with the proprietary nvidia driver, also enable the DRM kernel mode setting. If that does not work, too, check the instructions on the KDE wiki.

    As for the question of security, I want to emphasize that X11 is not increasing your risk of getting hacked. If one of your applications is compromised, then X11 acts as one method by which an attacker could further their attack or extract information, but other methods would usually be easier for an attacker. You could use flatpaks or firejail to mitigate those other methods, but only after you’ve done that would Wayland provide a meaningful security benefit.