macOS doesn't require developers to rebuild apps with each major OS release, as long as they link with system libraries and don't try to (for example) directly make syscalls.
Apple may require rebuilds at some point for their Mac Store (or whatever they call it), but it's not required from a technical perspective.
The one exception here is CPU architecture changes, and even then, Apple has provided seamless emulation/translation layers that they keep around for quite a few years before dropping support.
that's backwards compatibility. forward compatibility is being able to run new apps on an old operating system. the latest version of the SDK builds apps which only run on big sur or newer.
macOS doesn't require developers to rebuild apps with each major OS release, as long as they link with system libraries and don't try to (for example) directly make syscalls.
Apple may require rebuilds at some point for their Mac Store (or whatever they call it), but it's not required from a technical perspective.
The one exception here is CPU architecture changes, and even then, Apple has provided seamless emulation/translation layers that they keep around for quite a few years before dropping support.
that's backwards compatibility. forward compatibility is being able to run new apps on an old operating system. the latest version of the SDK builds apps which only run on big sur or newer.
The latest Xcode supports targeting back to macOS 11. This covers >99% of macs which is acceptable for most developers.
https://developer.apple.com/support/xcode/
that leaves out every mac made before 2014
At less than 1% why does it matter?