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 653543
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Not a good thing
by Kochise on Mon 5th Feb 2018 22:34 UTC in reply to "RE[3]: Not a good thing"
Member since:

Well, the 32 bits memory barrier is also dependent not only on PAE but also the BIOS's ability to offer memory remapping, which not everyone allows. My AMD A8 x64 get stuck at 2.25GB of RAM under Windows XP, not matter what, because of this stupid BIOS limitation, even though it features 8GB of memory.

I also understand your register concern, I'm a 68k and SH-4 assembly coder, and I know too well how much these ISA are vastly superior to x86, which despite its flaws bred pretty well its retard architecture at rabbit pace. AMD64 only closes a little bit the gap.

I've made quite challenging graphic processing using byte/word register swapping to avoid as much as possible memory access, abused 64 bits registers to do fixed point color scale dithering, with the expected throughput increase, so I can confess it works.

But the memory consumption, God, Windows x64 is just such a resource hog, Chrome or Firefox with ten tabs open will make any PC with "just" 4GB crawl like a dry snail. How can it be possible, how can it be just acceptable ?

Reply Parent Score: 1

RE[5]: Not a good thing
by ahferroin7 on Tue 6th Feb 2018 12:30 in reply to "RE[4]: Not a good thing"
ahferroin7 Member since:

Actually, that's the web browsers, not Windows (Chrome on my Windows system sits at roughly 750MB resident with the 16 extensions I use, but is still about 720MB on my 64-bit Linux laptop with the exact same set of extensions and tabs), although Windows is pretty damn bad too (about 20-50% higher memory usage than an an equivalent set of services on Linux).

The problem is that memory efficiency isn't really a developer priority unless they're working with particularly small systems, because it's not something that end users really notice in most cases (that is, if there are memory efficiency issues, they show up as performance issues for most end users). For the example I gave above with Chrome, that 30MB difference is essentially nothing as far as most developers are concerned (and TBH, with 16GB of RAM, I consider it not worth worrying about either).

Reply Parent Score: 2