[masklinn]

> In order to support 32-bit apps the OS needs to include 32-bit versions of all the system frameworks. So dropping support for 32-bit apps means cutting the size of all the system frameworks in half.

Less than half as 32b code objects will be smaller than 64b ones, but even if it's half how much storage is that exactly? I mean I probably have games bigger than the frameworks on my device.

> As for speedup/memory gain, merely launching a 32-bit app will cause the OS to get a bit slower / use more memory until such time as the app is actually killed by the system.

Well yeah so it's just pay for what you use aka who gives a shit.

> And if you have any 32-bit apps that actually do background processing

Which is unlikely given the vast majority of applications being killed by this move are games.

I mean let's be honest for once, the gain from removing 32b frameworks is pretty much entirely on Apple's side, there's little gain to be found for end users when they're not just plain losing value in this move.

[eridius]

> I mean let's be honest for once, the gain from removing 32b frameworks is pretty much entirely on Apple's side

I've given you multiple concrete benefits to end users. You may not personally care about the code size difference, and you seem to be completely discounting the speed / memory usage issues, but just because you personally don't think those are a big deal doesn't mean they don't actually exist.

[masklinn]

> I've given you multiple concrete benefits to end users

There are not benefits since they break software. You can get pretty much all of these by just removing remaining 32b software from your system.

[eridius]

Two things:

1) Just removing all 32-bit apps doesn't recover the disk space used by the 32-bit versions of frameworks, and

2) If you remove all 32-bit apps, then there's literally no point to retaining the 32-bit OS support anyway.