• misk@piefed.socialOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          24 hours ago

          I tried to search as wall and came up empty - sorry! My best guess for this brainfart is that Valve dropped support for 32-bit on Mac relatively recently and that was after Mac client has been 64-bit for quite some time.

          • BootLoop@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            6
            ·
            23 hours ago

            Not worried about storage but it adds a mess of packages and if I remember right in some cases you need to add i386 repositories into the sources list. As for the game libraries, they’re generally kept contained when downloading from Steam. Besides, any old Windows games will have the runtimes handled by Proton and new Linux native games are new enough to be 64 bit.

            • sugar_in_your_tea@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              5
              ·
              edit-2
              22 hours ago

              If you install the flatpak, you won’t need to deal with those dependencies.

              Adding a repository really isn’t asking for that much. It took like 30s back when I used Arch, and it works OOTB on my current distro family, openSUSE. On Windows, the installer handles it.

              It really isn’t something that anyone should care about.

              • Trashbones@lemmy.sdf.org
                link
                fedilink
                English
                arrow-up
                3
                ·
                22 hours ago

                The flatpak version can have issues integrating with the system, while the native install generally has fewer issues. These issues can crop both in the steam client and in the games themselves (since those processes are also sandboxed).

                I personally can’t use the flatpak version on my desktop (Fedora 42) because I can’t get hardware acceleration working on the flatpak client and it’s unusably slow. Other issues I’ve heard about with the games themselves running poorly also makes me disinclined to even try to fix it.

                That being said, Fedora has a nicely packaged native install for the steam client, maybe if I had to manage the dependencies more I would feel differently.

  • rozodru@piefed.social
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    4
    ·
    1 day ago

    I now feel sorry for that Fedora dev/maintainer that got thrown over the coals earlier this year for suggesting Fedora drop 32bit now that everyone seems to be, indeed, dropping 32bit.

    • Keegen@lemmy.zip
      link
      fedilink
      English
      arrow-up
      33
      arrow-down
      1
      ·
      1 day ago

      This is a completely different thing, Steam is dropping support for 32bit operating systems. Fedora hasn’t had a 32bit release since version 31. What that proposal was about was dropping 32bit packages, which would break old 32bit games (and Steam itself, as it relies on a lot of 32bit libraries as well).

    • Laser@feddit.org
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 day ago

      Pretty sure it’s just that Steam will no longer function on 32 bit machines, not that it will no longer be able to launch 32 bit binaries. The latter would make it impossible to run your old games. The fedora proposal would have running 32 bit libraries on 64 bit systems impossible as well, as it included dropping multilib.

  • Frezik@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 day ago

    The first x86-64 processor came out in 2003. Technology sure does move fast.

    Edit: checked my old Newegg orders. I bought my first x86-64 processor, an AMD Athlon 64 3200+, in Jan 2005. I seem to remember games were starting to pick up 64-bit support around then (I think Eve Online in particular, which I played a lot back then), so it made sense to switch.

    • Quetzalcutlass@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      And when 64-bit support first came to Windows, Microsoft artificially limited the amount of RAM you could use unless you shelled out for the much more expensive editions. On Vista you were arbitrarily limited to 8 gigs with the basic edition, 16 with premium, and even the business editions had a limit of 128 gigs, a tiny fraction of the addressable space under a 64 bit architecture.

      Even now there’s a limit, though it’s insanely high (over a terabyte) and you’re unlikely to ever see it unless you’re running a server on Windows instead of Windows Server (still limited, but in the dozens of terabytes) or Linux (which has a “limit” in the petabytes).

      • Frezik@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        Eh, not that big of a deal. The exact same order where I got the 3200+ also had a stick of DDR 400 at all of 256MB. I don’t think dual-channel memory was even a thing yet, or I’m sure I would have gone that route. That 8GB limit was a long time off.

    • stoly@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      In that case, your OS (Windows) can run 32-bit apps. The Steam application itself won’t have a 32-bit version at some point soon.

      • Owl@mander.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        15 hours ago

        I mean, isn’t the steam client 32 bit ? I always have to enable 32 bit repos to install it