2 ms·
Maybe 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 lib
by wtallis 9y ago
Maybe 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.