• Natanael@infosec.pub
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 day ago

    No, Wine (and Proton) is a compatibility layer (API translation, etc). Containers is an isolation method which hides the details of the OS from the software and gives it a standardized environment.

    https://github.com/ValveSoftware/steam-runtime

    No matter what Linux distribution you run Steam on, the only thing you need to do is to get the container system up and running. Once that runs, all software that runs in these containers will run on that device.

    • Appoxo@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 day ago

      So something akin to flatpak/snap?
      Isnt that the purpose and source of controversy vs distributing them the usual way of repositories?

      Edit: Had some time to read the README.
      Very interesting. But that sounds, like a vendor lock-in. Essentially devs are forced to use the Steam SDK to make it executable on Linux or face the issue of checking the compatibility of every distro, no?

      • Natanael@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        20 hours ago

        No, the container environment uses default open source libraries. You don’t add any Steam dependencies to make software run in that environment. You can run it without Steam too. It’s just that Valve are the ones maintaining and updating this particular packaging of containers. When Valve releases new versions of their container (including updated default system libraries), you have to test compatibility with it or stick to using an older one. Similar to how Windows software versions would work best with different Proton versions.

        You can use the Steam SDK when using it, and you can also choose not to.

        Flatpack is a separate thing, which only handles Linux software within the regular desktop environment (a different method for packing software dependencies, managing system permissions, etc). The main difference is that Flatpack software can integrate with the regular Linux desktop environment, but the container based solution is fully separate from it (runs in gaming mode).

        • Appoxo@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          19 hours ago

          Sounds interesting and eases my concern about the dependency on large corporations.

          PS: What I meant by comparing Flatpack with the packaging from the SteamSDK is the general idea behind it (e.g. containerizing and isolating from the OS).

        • Appoxo@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          21 hours ago

          So what if Steam stops development of the SDK or turns evil?
          What other choices do devs have if they want to keep their systems compatible with all distros?
          It looks to me as if you can either rely on proton/WINE or be stuck with the SDK if you run native.

          • prole@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            20 hours ago

            Proton often works better than native Linux versions of the same game.

            Just use Proton. Seriously, if you haven’t gamed on Linux in a long time, it’s mind blowing how well it works.

            • Appoxo@lemmy.dbzer0.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              19 hours ago

              Like I mentioned: I am gaming quite a bit (lately more on it than on my regular PC) on my SteamDeck.