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.

Thread beginning with comment 653469
To read all comments associated with this story, please click here.
BlueofRainbow
Member since:
2009-01-06

The only positive aspect of the story is that users will be warned ahead of 32-bit support completely disappearing and that the application just lunched will not run on the next macOS upgrades.

Depending on the set of applications the user has, there will be a choice between:
- freezing macOS to the current version to retain 32-bit support
or
- shelling out much money to upgrade the most valuable applications, if the vendors are still in business and continuing to maintain these applications.

Another down-fall - what about all those games one may have collected over the years?

Reply Score: 5

bugjacobs Member since:
2009-01-03

Backwards compatibility has never been a Apple force ... (?) Just look at Adobe software ..

Reply Parent Score: 4

sklofur Member since:
2016-03-28

Remembering that the original Mac came out in 1984, a G5 Mac shipping in 2006 could run almost all Mac software released up to that date. The Classic MacOS was a flawed product (necessarily of its time) and most of its internal technologies weren’t changed much after System 7 (with a couple of exceptions), so the Classic environment could run almost everything that shipped.

Even after the Intel transition, a Mac running Snow Leopard could still run almost every OS X title released to that point. Apple’s penchant for breaking compatibility came with the release of Tiger. Sure, Classic didn’t make it to Intel, but I suspect that was more due to technical issues.

In and of itself, I don’t mind this so long as there remains a viable way to run the older software without needing old hardware.

Edited 2018-02-04 00:20 UTC

Reply Parent Score: 2