I really hope developers stop requiring 10.15

[scaramoosh]

I've noticed this a few times now with the App store, it saying the app requires 10.15 or later.... why? Needless restriction unless Apple are pushing it.

I'm not going to upgrade without 32bit support, no reason for taking it out other than Apple being lazy. Microsoft managed it, Microsoft managed it and bringing Windows to ARM, so why not Apple?

I've built a new Windows PC again, all this does is means this iMac is the last I buy.

 

[DeepIn2U]

I highly doubt that Apple is ever going back to their OS supporting 32-bit code anymore. Maybe within Parallels/Fusion for 64-bit OS and therein once booted supporting 32-bit apps - yet not within macOS. Apple gave notice to all developers still currently coding in their API or other IDE's over a year that 64-bit apps is all that is supported going forward.

Xcode will no longer download from the App Store on macOS Mojave as I found out last week as I upgraded my Mac. Should you purchase an iMac I highly doubt it'll ship with Mojave ~ unless it's an older model (say mid-2019 or earlier).

 

[chrfr]

I've noticed this a few times now with the App store, it saying the app requires 10.15 or later.... why? Needless restriction unless Apple are pushing it.

They’ll eventually stop requiring 10.15, and move on to 10.16 or whatever the next major OS is called.
It’s not a needless restriction to move the minimum operating system forward. Developers may want to use features only available in 10.15, or perhaps they just don’t have the resources to support a lot of versions.

 

[scaramoosh]

It is a needless restriction, people on Windows always expose developers who pull these stunts. They'll have a 10kb file that allows it to work all of a sudden.... always the way.

 

[Ritsuka]

There are a lot of new API in 10.15. There is way to make some apps work in a previous macOS version (UIKit apps, 3d games using 10.15 features).

 

[chrfr]

It is a needless restriction, people on Windows always expose developers who pull these stunts. They'll have a 10kb file that allows it to work all of a sudden.... always the way.

That isn't the case with Mac apps that are built using the latest features which actually require 10.15.

 

[nshinka]

It is a needless restriction, people on Windows always expose developers who pull these stunts. They'll have a 10kb file that allows it to work all of a sudden.... always the way.

Windows has way more backwards compatibility than macOS, because it's designed to please enterprise users who hate change and want to upgrade as little as possible. Apple forces change forward, which is good in some ways and bad in others. Use Windows if you want to be able to use the same OS version for 5+ years with no feature updates and have most applications work.

 

[FilthyMuppetInnuendo]

It is a needless restriction, people on Windows always expose developers who pull these stunts.

OS X isn’t Windows, though. OS X actually gets updates. OS X was rebuilt from the original Mac OS decades ago. Windows still emulates serial and dedicated printer ports, even for LAN and Internet connections because the developers are either too incompetent to build something new, too lazy to rewrite the OS to modern standards, or too terrified of changing code they don’t understand for fear of breaking the one thing they know works. 32-bit anything is a major problem with a doomsday timer of only 18 years now. When 2038 rolls around (assuming, you know, the world magically hasn’t had other, more pressing and severe problems which we know will happen), everything that still relies on it will crash horribly. Even early OS X had that problem, but… Apple fixed it. By deprecating old frameworks. Not just building on top of them and hoping everything still works by using a ****-ton of code “voltage adapters” and emulation “duct tape,” like some kind of horrible kit bashed Power Rangers enemy.

You really need to switch away from 32-bit applications. Apple started this transition roughly 12 years ago.