6 ms·
Steam to End Support for macOS Mojave and 32-Bit Games
- gs17 3y agoTitle makes it sound too much like Valve is making the decision and that it's not a Mac-only thing. Apple is who chose to end 32-bit support.
- olliej 3y agomacOS was 64bit by default more than 16 years ago[1], and has only operated on 64 bit hardware for almost 15 of those years, only dropped 32bit 4 years ago, and Apple literally no longer sells any 32bit hardware. It was game developers who chose to keep producing 32bit software for more than a decade despite it clearly being a deprecated architecture, and clearly having no future, that created this problem. Developers have had more than enough time and notice to switch to 64bit, and chose not to. I see HN talk about MS being stupid for supporting decades of weirdness, and I see HN talking about how bad Apple is for not doing the same thing. You can't have it both ways: either you support everything indefinitely no matter the cost, or you move forward and require developers to actually pay attention to deprecation information. [1] Minor edit, macOS had 64bit kernel and bsd layer before leopard for ppc64 but iirc a lot of the UI layer frameworks (Cocoa, etc) had issues that meant it was not really a 64bit OS from an normal user PoV
- eqvinox 3y agoThe real problem is that — to my knowledge, please correct me if I'm wrong — you can't install a 32-bit environment as a container/subsystem/… on OSX. For both Windows and Linux, you can throw 32-bit components into an appropriate place and it'll work, while the rest of your system is 64-bit native. That said, I agree game developers were/are being slowpokes on this. For games shipped as 32-bit 10 years ago you can use emulation techniques now because you have 10 years of performance gains to sink into the emulation. But more recent stuff shipped as 32-bit is in a special bad place since it may rely on "current" performance…
- olliej 3y agoCorrect, the macOS 32bit OS had an array of design decisions that impact large aspects of the system as a whole, and so it was deprecated - a large number of the APIs added after 2009 were 64bit only - and then removed so the OS could remove the various support infrastructure needed for that - recall that iOS shares a bunch of the core OS and dropped 32bit hardware entirely before "Apple Silicon" happened so you complicate everything for a deprecated platform. Then of course you run into the whole "there is no 32bit hardware at all" thing on the last few generations of mac hardware. Supporting old hardware is not free (engineering time is the issue, presumably not money :D), supporting what is in essence an entire dead platform is even worse. It also means that those games and software that are 32bit (or in the case of steam, Intel only) have significantly increased overhead on the system - you suddenly have to map in essentially an entire copy of userspace, and there are likely indirect overheads as well due to page table nonsense, etc. This is before we get to things like rosetta.
- freedomben 3y ago> I see HN talk about MS being stupid for supporting decades of weirdness, and I see HN talking about how bad Apple is for not doing the same thing. You can't have it both ways HN is not a monolith. There are people on here that hold each of those opinions, and there's no inconsistency because two people on HN are separate entities that can have different opinions. HN is in fact a great place for those people to have a discussion.
- duskwuff 3y agoRe. [1]: ppc64 on macOS was always an afterthought. It was only available on G5 systems, so developers couldn't ever rely on it being available, since the Powerbook and Mac Mini were G4 to the bitter end. And, as you mention, there was a long period where the GUI libraries weren't available for ppc64 (probably because they depended on 32-bit Carbon on the back end), so using it required developers to run 64-bit code in a separate process. From what I recall, the performance benefits weren't even that dramatic (and were only available on the G5 which was already pretty fast for the time), so very few developers bothered building for ppc64 unless they really needed the larger address space.
- dangus 3y agoThe only thing I think that sucks about this is that there is no software emulation or translation alternative that can allow you to run 32-bit macOS apps besides literally running the entire Mojave operating system in the background. Something like DOSBOX or Wine but for 32-bit Mac apps would be great. (This exists but not in a capacity that can run games) I also think that games are uniquely well-suited to running them far in the future. Most productivity apps are either replaced by something else or have a new version that I can migrate over to. When it comes to games, they are typically one-time art pieces. A game like Morrowind is just as “useful” as it was 20 years ago. Sure, I can play it with a community game engine, but not all games are popular enough to get that treatment.
- qup 3y agoI love this game. Although after enough playtime, I found boots of blinding speed to be a necessity. (Blocking the blinding effect, of course) I wonder why they took levitation out of the later games
- Rebelgecko 3y agoBelieve it or not, some people like playing games that were made before the 64 bit transition happened. Not every good game is a constantly updated live service.
- olliej 3y agoThe macOS 64-bit transition happened before steam for Mac was released. The was a single year between steam for Mac being released and 64bit hardware being a requirement for macOS. There was never a reason for anything published in the steam store to be 32bit only.
- st3fan 3y agoThis. It was also 100% clear that 32 bit was going to end at one point. Apple was extremely clear about that and provided all the tools and documentation to help developers make the transition.
- eviks 3y agoHow does "extreme clarity" remove any of the top barriers to transition? (also Apple docs aren't good, so I think "all the tools and documentation" statement is not true)
- gpderetta 3y agoAnd game developers decided that the churn was not worth it.
- bonton89 3y agoGame development, particularly of that era, made the lion's share of sales in the first year or two after release. The fact that 32-bit was going to end was never going to be a relevant consideration. This isn't IBM fulfilling a 10 year service contract. They made a game that worked on Apple PCs that existed at the time, users bought it and it did. If the users wanted it to work 10 years later then they could always fire up a vintage Mac.
- ben-schaaf 3y ago
- idonotknowwhy 3y agoIt's different people commenting on these issues within HN
- fomine3 3y ago32bit application is completely fine on Windows, and games are made for Windows. I don't say Apple is bad, but just it's not a platform for native games.
- Hammershaft 3y agoCreating conditions where game development requires constant maintenance literally just to be usable on a shifting OS platform ultimately tilts the economics of gamedev towards significantly worse games. Great example of this is the iOS game store, which is an endless wasteland of manipulative skinner boxes. Great example of this is a studio that once made excellent games on iOS, Vlambeer: https://variety.com/2019/gaming/features/android-ios-apple-google-game-dev-problems-1203191551/# https://variety.com/2019/gaming/features/android-ios-apple-g...!
- gpderetta 3y ago> I see HN talk about MS being stupid for supporting decades of weirdness, I see it almost universally praised on HN.
- nick_ 3y agoFriendly reminder that support != able to run. This seems totally reasonable to me. Are there many games played today which are A) 32-bit only and B) still need fixes/patch/update support?
- duskwuff 3y ago> Are there many games played today Most of Valve's own games are (still!) 32-bit only on macOS, including all of the Half-Life games, both Portals, Left 4 Dead, and Team Fortress 2. The only major game of theirs which is available for 64-bit macOS is Dota 2. (Underlords and Artifact were both market failures, so I'm ignoring them.) Really, the way Valve has handled the 64-bit transition on macOS has been pretty terrible. Up until today, their recommended "solution" for running 32-bit games was for users to downgrade to Mojave or install Windows through Boot Camp. (Never mind that neither of these is an option for users with newer computers.)
- sosodev 3y agoRight? I know Mac users are a fraction of the market but recompiling nothing almost seems petty.
- duskwuff 3y agoThey even did a bunch of work on Half-Life recently for its 25th anniversary [1], including adding Steam Deck support and fixing long-standing bugs -- but that didn't extend to making it run on any modern macOS system. [1]: https://www.half-life.com/en/halflife25/ https://www.half-life.com/en/halflife25/
- appplication 3y agoI’ve been wanting to play portal 2 for years but I’m astounded Valve is unwilling to prioritize the relatively low amount of work it would take to compile to 64-bit.
- deleted 3y ago[deleted]
- zlg_codes 3y agoThis sort of stuff is unsurprising. This is alongside losing Win7 support next month because Valve was stupid and built on Electron, so Google dropping support means Electron in general loses Win7 support. How long before Steam requires a TPM to run locking me out of my games?
- johnny22 3y agoDon't they use Chromium Embedded Framework and not electron? They are not the same thing even if they can allow to do most of the same things.
- zlg_codes 3y agoThere aren't enough differences for them to be big enough. Google still controls both and deprecated Win7 support as of Jan 1st. The facts are still the facts, doesn't matter how much we 'ackshually' on the name itself.
- puffgridda 3y ago[flagged]
- fomine3 3y agoSteam is one of an application that embedding browser really makes sense.
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- calamari4065 3y agoHonestly, expecting 32 bit games from the previous century to keep working on modern machines forever is not a reasonable ask. 8bit and 16bit applications don't run natively on modern hardware, where's the outrage for those games? Like old DOS games, your options are to run on period hardware or virtualize. Modern systems are so far removed from these old 32 bit systems that they may as well be a Commodore 64. It's time to let go.
- eviks 3y agoHonestly, a few decades isn't even a century, let alone forever, and the 8bit games are much worse re e.g graphics, so fewer people are outraged since there are better alternatives, also, if non-native way to run is an option, that also dampens outrage
- Apocryphon 3y ago> Like old DOS games, your options are to run on period hardware or virtualize. Great. Where's the virtualization layer for running 32-bit apps on macOS?
- exabrial 3y agoWhy the in actual hell did we have to kill 32 bit support? Just seems ridiculous to break that sort of backwards compatibility
- lxgr 3y agoNot having to ship all libraries, first, and third party applications in effectively three versions (x86-64, amd64, arm64) saves significant disk space. A mixed 32 and 64 bit environment also means having many libraries paged into memory twice, and Apple isn't exactly known for being too generous on their RAM specs.
- eviks 3y agoCan save disk space by making the components optional
- lxgr 3y agoThe OS volume on macOS is read-only these days, and due to how universal binaries are implemented, just putting a 32-bit version somewhere else would probably not work without a major redesign (in addition to making them more vulnerable to tampering compared to the read-only volume).
- eviks 3y agoIt's read-only for the user, not for the system (after all, OS can update itself)
- mrpippy 3y agoKilling i386 support allowed: - dropping the “legacy” ObjC runtime, which lacked many features of the “modern” runtime that all other Apple platforms use. In particular, Swift couldn’t be used in system frameworks as long as the legacy runtime was still around. - dropping the Carbon APIs, which were an entire alternate API surface only usable by 32-bit apps. Lots of old, obsolete stuff here that very few apps were using: QuickDraw, QuickTime, HIToolbox, Font Manager, etc. - Disk space savings from not having to ship i386 slices