• FooBarrington@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    3 days ago

    Why the fuck is it weird for a client to run inside a runtime environment with well-defined library versions, when that client has to ship that runtime environment anyways to ensure the games can actually run on a broad range of systems?

    Oh, sure, it’s so much better if the client relies on system libraries instead. Yes please, I like incompatibilities and issues with debugging. So much better than loading a different set of libraries. Stupid Valve!

    • TheTechnician27@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      3 days ago

      Alright, let’s just ignore the containerization because of the problem Valve creates by making you open Steam when you play games you paid for. It’s just 64-bit for the runtime, not even the client itself. It’s 2026. I’m not going to act like this is noteworthy or an accomplishment.

      • Jako302@feddit.org
        link
        fedilink
        English
        arrow-up
        9
        ·
        3 days ago

        You can run steam games without opening steam as long as they don’t use the steamworks DRM or require an additional login (Ubisoft, Bethesda). Both of these issues are created by the developers / publishers, not steam.

      • FooBarrington@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        3 days ago

        Do you even know what any of the words you’re using mean? It doesn’t matter whether the Steam client is running in the runtime, you still want the same containerization to run your games, because that’s how they make sure the games run everywhere.

        You’re just angrily flinging shit around without understanding what any of this is about. Don’t you have anything better to do?