4 ms·
Does it mean macOS users won't be able to play 32-bit games in Wine anymore?
by shmerl 9y ago
Does it mean macOS users won't be able to play 32-bit games in Wine anymore?
- godzillabrennus 9y agoI’d imagine that’s the case.
- pvg 9y agoIt doesn't, 32 bit apps still run, Wine and Wine-hosted apps included.
- throwaway2048 9y agopresumably they are going to scrub 32 bit support entirely, including from the kernel.
- pvg 9y agoEventually. Certainly not in this or next major release and the rate of adoption/updates will very likely influence the schedule. There are a lots of widely used apps out there that are 32 bit. Steam, for one, which probably matters more in that market segment than Wine.
- shmerl 9y agoI suppose for those who play games on macOS, it's not Steam itself that's a problem, but quite a big amount of actual 32-bit only games. Both macOS and Windows ones (that could run in Wine until now). I hope when Linux distros will start dropping 32-bit support, they'll still keep multiarch around for such purposes.
- pvg 9y agoRight, but that's the gist of what I mean - I don't think 'macOS update that suddenly and irrevocably kills most of your Steam library' is on the horizon.
- danieldk 9y agoWhy not? on iOS they started warning on starting 32-bit apps in 10.3 and killed 32-bit app support in iOS 11. I can imagine that they will be a bit more gentle with macOS, given its longer history, but I wouldn't be surprised if they yank all 32-bit system libraries in High Sierra + 2. This is typical Apple and has it upsides (unlike Android/Windows, applications do not rely on ancient APIs) and downsides (breaks compatibility). Also, part of the motivation here may be to kill Carbon as soon as possible. If Marzipan materializes, they probably do not want to maintain Carbon, AppKit, and Marzipan/UIKit simultaneously.
- macintux 9y agoFebruary 2015 was the deadline for apps to support 64 bits with any new updates in the App Store. So developers had 2.5 years to prepare for iOS 11. Users had less warning, true, but the situation was different since they also had no way to acquire apps outside the App Store.
- jammi 9y agoYou can still have VMs for 32bit games, and if there's a big demand for them, bet on someone creating a gaming-oriented VM.
- chungy 9y ago> I hope when Linux distros will start dropping 32-bit support, they'll still keep multiarch around for such purposes. A bit late for the comment there. Pretty much the only distros that still support x86-32 as an installation/host option are Debian, Slackware, and Gentoo. Everybody else (including Ubuntu) has gone 64bit-or-bust. Mind that the latter half still applies. The kernel is still capable of running 32-bit applications in a 64-bit environment, and no distro has removed multiarch support, and likely won't.
- shmerl 9y ago> and no distro has removed multiarch support, and likely won't. My only concern is, that with general dropping of 32-bit, multiarch versions of packages will be bitten by bit rot, because no one will be maintaining them.
- lmm 9y agoWell, if people are using them those people will report bugs, if no-one is using them then they will rot but it won't matter. It hurts if you're using one obscure package that no-one else is, but that's the software life. /I was quite possibly the last gentoo/sparc32 user
- 0x0 9y agoApple has in fact stated that High Sierra is the last major release to run 32bit apps "without compromise" (their words). So probably a macOS 10.14 could show up in a couple of months at WWDC without 32bit app support, just like iOS 11 did last year.
- macintux 9y ago> So probably a macOS 10.14 could show up in a couple of months at WWDC without 32bit app support I don't understand your reasoning. They're implicitly (but strongly implicitly) saying 10.14 will run 32-bit apps. What's uncertain is what "compromises" they'll entail. Even Apple wouldn't drop all support for 32-bit apps with just a few months' warning. They're ruthless about moving forward, but not quite that cruel.
- 0x0 9y agoBut that's exactly what they did in iOS 11?
- pvg 9y agoThey also announced exactly that. Not the case for this or the next major revision of macOS.
- macintux 9y agoFebruary 2015 was the deadline for apps to support 64 bits with any new updates in the App Store. So developers had 2.5 years to prepare for iOS 11.
- 0x0 9y agoAdditional requirements for new apps or updates to apps is something completely different from disabling existing purchased apps and denying end users access to their documents contained within.
- 9y ago
- wtallis 9y agoMaybe in the distant future. Last I checked, Wine could still run 16-bit programs on macOS. I could see a 32-bit Wine needing to bring its own copy of more libraries that Apple wants to stop shipping two copies of, but I doubt Wine would be much affected by not getting access to new 64-bit only APIs.
- shmerl 9y agoOn Linux, Wine requires 32-bit libraries to run 32-bit games, even if it's 64-bit Wine. I'd imagine same applies on macOS. So if let's say they'll drop support for 32-bit OpenGL, there isn't much Wine can do about it.
- wtallis 9y agoRight, but I doubt Apple will go that far, especially in the next few years. They have strong reasons for abandoning 32-bit (or at least breaking binary compatibility) for the stuff written in Objective-C, but they'll probably leave the basic Unix/C stuff alone.
- comex 9y agoThe ‘basic Unix/C stuff’ includes most of the architecture-specific code, in both the kernel and userland, so keeping it around would have a large cost. And there wouldn’t be much point: command line tools are probably much more likely to be 64-bit than GUI apps, as they’re more likely to be open source (allowing recompiling even if the original developer is gone), and more likely to be portable between operating systems (reducing the chance of running into either architecture-specific dependencies, or macOS APIs that happened to be deprecated with the move to 64-bit).
- Someone 9y agoThey can write a 32-bit OpenGL API that calls the system’s 64-bit OpenGL, or does everything in software and renders to a memory range that they somehow make show up on the screen.
- sitharus 9y agoNo, it means MacOS will no longer have a 32-bit runtime but this does not prevent the CPU executing in 32-bit mode - just that all system calls have to happen in 64 bit mode. Wine will have to be a 64-bit application linked to the 64-bit libraries and do a bunch of thunking and mode switching, but it already does this to support 16-bit applications. I have no idea how easy this is but the the OS already does it to support 32-bit applications running on the 64-bit kernel.
- shmerl 9y agoWhen Wine runs 32-bit application, it links against 32-bit libraries, including OpenGL. So how would that work in pure 64-bit system? 16-bit is really some special case, I don't know how Wine is doing it, but I suppose it does some special translation.
- sitharus 9y agoThe same way those 32-bit libraries call the kernel now - they marshal the call to 64-bit land. A lot of the user space is compiled separately for performance and to maintain ABI compatibility so this would have to be taken up by a third party. I would expect to see a slowdown but it depends on the exact nature of the changes.
- caf 9y agoYou can only execute in 32-bit mode if the kernel gives you a compatibility-mode descriptor in the GDT, or lets you put one in the LDT. (or you use virtualisation)