Linked by Thom Holwerda on Sat 3rd Feb 2018 14:15 UTC, submitted by Drumhellar
Mac OS X

When users attempt to launch a 32-bit app in 10.13.4, it will still launch, but it will do so with a warning message notifying the user that the app will eventually not be compatible with the operating system unless it is updated. This follows the same approach that Apple took with iOS, which completed its sunset of 32-bit app support with iOS 11 last fall.

This is good. I would prefer other companies, too, take a more aggressive approach towards deprecating outdated technology in consumer technology.

Permalink for comment 653458
To read all comments associated with this story, please click here.
RE: Comment by Kroc
by Brendan on Sat 3rd Feb 2018 15:25 UTC in reply to "Comment by Kroc"
Member since:


I'm certain this is one step toward moving away from Intel chips. A chip that has no 32-bit hardware at all is going to require a significantly less number of transistors and therefore less heat / more room to do something else. It's also much easier to emulate or transpile the Intel code if you're only dealing with one (much cleaner and newer) arch.

For 80x86, the only major difference (for user-space code) between 32-bit machine code and 64-bit machine code is that 64-bit machine code is allowed to have "REX prefixes". In other words, deprecating 32-bit apps wouldn't make any difference for application emulators - they'd still need to emulate all 32-bit instructions to make 64-bit code work (excluding an extremely small number of instructions that were recycled to make room for REX prefixes - mostly one "inc" and "dec" group of opcodes).

The reason Apple is deprecating 32-bit applications is much more likely to be related to the cost of maintaining a compatible kernel API and shared libraries.

- Brendan

Reply Parent Score: 9