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 653520
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Typical Apple
by Kochise on Mon 5th Feb 2018 10:56 UTC in reply to "RE[3]: Typical Apple"
Member since:

I understand your concerns about 64 bits performance and less 32 bits support bloat. However I would have to wonder why browsers needs so much memory nowadays, web pages doesn't features 4K pictures. Coders should be more frugal about memory consumption.

Apple chose Intel because of deal, better overall performance and power economy in 2006 face to AMD's offering, and also the integrated Wifi AMD was lacking (the whole Centrino stuff).

Apple made the transition in early 2006 when the Core 2 Duo would only be available later that year, once the first Intel Mac were shipped with 32 bits cpus.

Reply Parent Score: 1

RE[5]: Typical Apple
by Kochise on Tue 6th Feb 2018 06:13 in reply to "RE[4]: Typical Apple"
Kochise Member since:

Was there such matter to downvote, really ? God, tech peoples' believes are fragile these days.

Edited 2018-02-06 06:13 UTC

Reply Parent Score: 1

RE[5]: Typical Apple
by feamatar on Wed 7th Feb 2018 00:43 in reply to "RE[4]: Typical Apple"
feamatar Member since:

High memory consumption is due to aggressive caching strategies to get you faster reload times. Many people visit the same sites over the day, and to improve load times it is reasonable to cache whatever is possible and keep it in memory. If you load a web page that is 40MBs, the next time you visit, it can load as little as 1MB, and no, it won't use hdd cache when you have enough ram available.

Reply Parent Score: 2