this post was submitted on 09 Jul 2025
75 points (88.7% liked)
Gaming
32076 readers
349 users here now
From video gaming to card games and stuff in between, if it's gaming you can probably discuss it here!
Please Note: Gaming memes are permitted to be posted on Meme Mondays, but will otherwise be removed in an effort to allow other discussions to take place.
See also Gaming's sister community Tabletop Gaming.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The steam client has nothing to do with the games it launches.
Process.Start() works on 32 bit or 64 bit processes…
They are on 32 bit because they don’t need to upgrade to 64 bit and it’s likely too complex to upgrade.
Visual Studio, which actually benefits from 64 bit, just recently upgraded because these massive software stacks are difficult to update.
They keep a bunch of 32-bit libraries for backwards compatibility with older games that they launch. You can find numerous discussions about this in the Steam forums as well as on sites like Hackernews.
If you want, I can give it to you from a Valve employee:
https://github.com/ValveSoftware/steam-for-linux/issues/179#issuecomment-267790879
Maybe do some cursory research before talking out of your ass.
You just proved my point.
Runtime environment != the steam client.
Starting a 32 bit process (ie, process.start()) means nothing to the 32 bit steam client.
They can upgrade the steam client to 64 bit without affecting the launched games. that’s the point I was making.
They just haven’t.