> so this doesn't know about the major iCloud updates, or Apple Intelligence, or UI changes

I'm not familiar with macOS: Why would an application need to be updated for any of these? Were the existing APIs insufficient to integrate these?

▲

kstrauser an hour ago | parent [-]

Yes, and that's universally true for all APIs. All of those have added new features that are widely adopted by other apps, and the older apps can't automagically start using new features without using a newer API, or having code added to take advantage of them.

For instance, an app can't start using Apple Intelligence if it's compiled with an older version of the SDK that doesn't know that such a thing exists. There are some UI exceptions, such as if the OS starts rendering high-level requests like "draw a button" in a newer style. Lots of other things take specific application support, though. MacOS 14 added desktop widgets. Unless an app adds code to configure and deploy widgets, that's not something the OS can do for it. That means that Yojimbo couldn't possibly offer widgets showing, say, the 5 most recently added documents.

If you're OK with not needing or wanting the newer features, and it doesn't rely on some old API that Apple deprecated, then sure, continue to use it! It's still a fine app. But each passing year means that all its updated competitors can do new things that it can't.

▲

debugnik 27 minutes ago | parent [-]

Thanks for the examples. I simply wasn't expecting the features you originally listed to require application support, I see they're more involved that I imagined.

	▲	kstrauser 17 minutes ago \| parent [-]
		You bet. Even with things like iCloud, any old app can store a file in iCloud Drive just like any other folder on the computer, but apps have to use the CloudKit SDK to use more advanced sync features. It keeps getting updated annually, so apps using an older CloudKit can't use features that've been added since then.