8 ms·
Apple's backward compatibility is poor, and particularly bad for games. The 32-bit apocalypse kills off a large subset of the Mac's already less-than-stellar ga
by musicale 7y ago
Apple's backward compatibility is poor, and particularly bad for games. The 32-bit apocalypse kills off a large subset of the Mac's already less-than-stellar game library; and on iOS it already broke many apps that I used, many of which will not be updated. To me it seems like Apple is going in the wrong direction - really I want them to add an x32 ABI to save pointer space for apps that don't need more than 4GB!
Stick with Windows/Steam/Consoles/etc. if you don't want a bunch of your games that you purchased to become unplayable every year (unless you add multi-boot to run the old, compatible OS, or run them in a VM, which usually works poorly.)
As I have mentioned before, it's a very annoying example of Apple shifting technical debt and maintenance work away from themselves and onto developers, and the overall maintenance burden is greatly increased.
I like how the platform moves forward, but I really wish that there were a way of getting desirable security patches and feature improvements in the OS without breaking all of my apps.
- qwerty456127 7y agoDoes this mean I won't be able to play 32-bit Windows games with CrossOver?
- zamalek 7y agoIt depends. * 64bit processes usually can't load 32bit modules, only a 64bit OS can (true for Linux and Windows, I'm not sure if it's true for x86 overall). There's a pretty good chance that only a 32bit CrossOver could load 32bit modules. * Has 32bit support been stripped from the kernel, or has it only been stripped from the installed dynamic libraries? I'd wager that it's stripped from, or partially stripped from, the kernel. Even if Catalina allows 64bit processes to load 32bit modules, the kernel would have to support it. There's a one in four chance your scenario is supported. CrossOver definitely couldn't magically voodoo a 32bit module into a 64bit one, as it's impossible to determine if a register/address is a 32bit integer or pointer; if it doesn't work today, it will probably never work. I'm not sure if macOS supports IOMMU, but an external GPU with a VM might be your saving grace here.
- duskwuff 7y agoSupport has been at least partially stripped from the kernel. Attempting to run a 32-bit executable yields an "invalid executable type" error.
- Wowfunhappy 7y agoGiven that the kernel is open source, I wonder how hard it would be for someone to add that back in...
- saagarjha 7y agoBuilding the kernel itself is non-trivial.
- kenada 7y agoNot currently, but Codeweavers is working on a solution. https://www.codeweavers.com/about/blogs/ken/2019/10/3/crossover-for-catalina-progress-october-3-2019 https://www.codeweavers.com/about/blogs/ken/2019/10/3/crosso...
- 0x0 7y agoDoesn't the apple watch run a 32bit-on-aarch64 abi?
- pjmlp 7y agoApple watch uses a variant of LLVM bitcode as deployment format. And no, it isn't raw LLVM bitcode.
- 0x0 7y agoI was talking about the arch/abi running on the os. Looks like it's called "arm64_32" (maybe it's similar to the linux abi "x32"?) Xamarin among others ran into a snag but it seems they could retool and convert from armv7k to arm64_32 for example https://github.com/xamarin/xamarin-macios/issues/4864 https://github.com/xamarin/xamarin-macios/issues/4864
- saagarjha 7y agoYes.
- scarface74 7y agoAs far as iOS is concerned, Apple got rid of 32 bit support in the processor itself allowing it to improve the processor. Keeping around old code increases the security vulnerability surface. For instance, there are at least a half dozen ways of representing a string in Windows. One of the earliest widespread vulnerabilities in Windows was caused by improper handling of string encoding where anyone could run DOS commands on a web server running IIS just by encoding the commands in the browser. https://www.sans.org/reading-room/whitepapers/threats/unicode-vulnerability-why-458 https://www.sans.org/reading-room/whitepapers/threats/unicod...
- mey 7y agoYour example is from 2000/2001. The same year OSX was first publicly released.
- scarface74 7y agoThat’s kind of the point - it’s gotten worse since then. Windows has become more bloated as they’ve added on more layers and refuse to drop backwards compatibility.
- jabl 7y ago> As far as iOS is concerned, Apple got rid of 32 bit support in the processor itself allowing it to improve the processor. That is slightly different because Apple is designing their own mobile CPU's. And indeed by dropping 32-bit ARM support they can simplify and improve their CPU designs. OTOH, Intel isn't gonna drop 32-bit x86 support from their chips just because Apple isn't making use of it.
- Twisell 7y agoYeah but maybe dropping 32-bit support is a necessary step before dropping Intel chips... They will face some* backslash now, but if/when they switch Mac to their own arm chips they might achieve a painless transition. *They announced 32-bit deprecation like a decade ago, will legacy users be pissed of? yes! Is it a excuse for developers that still relied on 32-bit support over the last decade? NO!
- m000 7y agoDropping 32bit support is game-over for gaming on macOS. The numbers already didn't add up for indie developers [1]. Even AAA game developers often ignore macOS because the ROI is just too low. And from the $5/month subscription how much will end up to the developers [2]? Essentially what Apple Arcade will end-up hosting is ports of run-of-the-mill mobile games. And I'd bet the advertised number of developers will diminish as soon as the agreements they secured for the launch expire. But if this is the kind of gaming you're interested into, you already have your iPhone/iPad. [1]: https://www.gridsagegames.com/blog/2019/09/sorry-mac-users-apple-doesnt-care-about-us-devs/ https://www.gridsagegames.com/blog/2019/09/sorry-mac-users-a... [2]: https://www.vice.com/en_us/article/43k4ww/its-hard-to-use-apple-arcade-without-wondering-how-developers-will-be-paid https://www.vice.com/en_us/article/43k4ww/its-hard-to-use-ap...
- olliej 7y ago... I mean sure, I love the idea of paying $60 for a game that throws away 15-20% of the performance by targeting an architecture that hasn't been supported by MacOS for more than a decade, rather than supporting an architecture that has been around for something like 15 years. But yes, apple is in the wrong here, and should continue to support hardware that they haven't shipped in 10+ years. I assume you're in the group that believes MS should be required to support XP forever.
- wtallis 7y ago> Dropping 32bit support is game-over for gaming on macOS. No, it isn't. There were never any 32-bit x86 Macs with decent GPUs. Dropping 32-bit support only affects games that were already old enough to be commercially irrelevant or games that rely on unmaintained third-party middleware that never got a 64-bit port. Those don't add up to enough to be a major impact on the Mac gaming market. There are plenty of other factors that are much more important, such as Apple's abandonment of OpenGL and preference for Metal over Vulkan.
- redwall_hp 7y agoA bunch of Aspyr titles (a sizable publisher of AAA ports) won't work with Catalina, and there are no plans for updates. These aren't old games for the most part: https://www.macworld.co.uk/feature/mac-software/apps-wont-work-catalina-3698142/ https://www.macworld.co.uk/feature/mac-software/apps-wont-wo...
- anthony_doan 7y agoAh, thank you guys for posting this. I'll hold off too. My macbook pro is 2013 and pretty old it overheat often if I play video. This update will definatedly exacerbate the problem.
- Razengan 7y agoRegarding games, Apple Arcade seems to be just what the Mac needed. I haven't evaluated the quality of available offerings yet, but they look good in the App Store previews, and I think they're all native Mac apps (not lazy ports), using Metal and everything. Although yeah, you can't really own any of those games and will always need a subscription, and some may be removed in the future.
- thesquib 7y agoI play games on my Mac when I can play them on my PC (travelling is one reason for this). I try buy my games DRM free on GOG, and play them either on Mac or through Steam streaming (yes you can load non steam games). My Mac game library is essentially wiped out by this. And yes, there's this Arcade, but I have no interest in playing for something which is locked down to one platform.
- Razengan 7y agoIf I want to play something and I already own that platform, why should I prevent myself from playing it because of its exclusivity? Do you boycott Xbox, Playstation, Switch, DS etc. exclusives too? What about Windows-only games that aren't on Mac or other systems? There are certainly thousands of those. Do you refuse to play those either?
- jabl 7y agoPresumably Apple is dropping x86-32 because they don't want to spend resources maintaining 32-bit support libraries, doubling their testing matrix etc. And now you want them to add a third ABI? (Even in the Linux world, which prides itself in supporting crap used by a handful of people globally, X32 is dead, to the extent it was ever alive.)
- gpderetta 7y agoX32 is dead exactly because, where 64bit is not needed, x86-32 is perfectly fine. I.e. the only practical reason not to go 64 is backward compatibility.
- jabl 7y agoIndeed. X32 is beneficial for an application that - Never needs more than 4 GB RAM (because it's not worth the usability downsides from having two binaries and letting the user choose which to use, just for a small performance boost) - Is performance critical - Performance is bound by memory and/or cache bandwidth - A large share of the program memory usage is due to pointers The intersection of all the above is just vanishingly small in reality. X32 was never more than a gimmick to score a few extra points in SPECcpu. And thus people rightfully ignored it.