top 28 comments

sorted by: hot top controversial new old
[–] 30 points 1 year ago (13 children)

Coolio, can we get the steam client to 64 bit as well?

  • source
  • hideshow 13 child comments
  • [–] [S] 2 points 1 year ago (2 children)

    IIRC this has been announced as well couple of months ago.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 1 year ago (8 children)

    Why do you want a 64-bit client?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 10 points 1 year ago (7 children)

    You need to download a bunch of i386 dependencies on Linux.

  • source
  • parent
  • hideshow 7 child comments
  • [–] -5 points 1 year ago (6 children)

    Are you worried about storage?

    You'd also still need most of those if the launcher was 64-bit if you install an older game.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 8 points 1 year ago (5 children)

    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.

  • source
  • parent
  • hideshow 5 child comments
  • [–] -4 points 1 year ago* (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 1 year 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.

  • source
  • parent
  • [–] 2 points 1 year ago (2 children)

    I'm not a fan of flatpaks. I try to avoid them when I can.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 1 year ago

    64-bit only

    Except thr client.

  • source
  • [–] 15 points 1 year ago (1 child)

    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.

  • source
  • hideshow 1 child comment
  • [–] 30 points 1 year 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).

  • source
  • parent
  • [–] 5 points 1 year ago* (last edited 1 year ago) (4 children)

    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.

  • source
  • hideshow 4 child comments
  • [–] 1 point 1 year ago (1 child)

    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).

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year 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.

  • source
  • parent
  • load more comments (1 reply)
    [–] 11 points 1 year ago

    It's frankly amazing that they supported it for so long!

  • source
  • [–] 2 points 1 year ago (1 child)

    Will this make steam x86_64 (instead of x86)???

  • source
  • hideshow 1 child comment
  • [–] 2 points 1 year ago (3 children)

    Isn't steam a full 32 bit program ?

  • source
  • hideshow 3 child comments
  • [–] 2 points 1 year ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments