It takes approximately nineteen thousand winedbg processes to fill up 32 gigabytes of RAM.

Is it angry at me because I blew up a steam locomotive’s boiler in Derail Valley earlier?

    • BoxOfFeet@lemmy.worldEnglish
      1·
      4 days ago

      Why is that? I use it because it convienient and it works (for me). But what’s a reason to not use it? Is it unstable, or resource intensive? I only have a couple of games less than ten years old.

      • Err(()).unwrap()@lemmy.worldOPM
        1·
        3 hours ago

        Is it unstable, or resource intensive?

        Yes and yes. Most of the Steam client is implemented, poorly, as a web app running in a web view derived from (I believe) an old version of Chromium. It’s needlessly resource-intensive, even more so than Electron apps. The suite as a whole uses its own libraries in ~/.local/share/Steam/ubuntu12_{32,64} and I’m pretty sure it still depends on some 32-bit-only things. The overlay sometimes causes ridiculous performance issues related to input events (I move the mouse and the game drops to single digit framerates) even if the overlay isn’t active. The Steam Input config utility is poorly designed and horribly implemented.

        Lately it’s also been trying to murder my PC.

        I love Steam as a service, but the client is in an unacceptable state.

      • TwilightKiddy@scribe.disroot.orgEnglish
        5·
        3 days ago

        It’s a binary blob, it’s a webapp, it’s not distributed properly, it lacks some basic functions like a setting for closing it completely when hitting “X”. We no likey.

        • xilophor@lemmy.worldEnglish
          2·
          2 days ago

          iirc they have both a 64-bit bit version and a wayland version of steam on the beta branch, so they’re at least branching out (though it remains proprietary and almost certainly always will)