How you can write entries in the unified log which are informative, easily retrieved, and extremely simple.
scripting
If you’re running an interpreted/JIT language, Big Sur could return that it’s either 10.16 or 11.0, depending on the version of the environment.
macOS 11.0 will identify itself differently according to the SDK used, and an environment variable does the same for scripts.
How does Big Sur convince older software that it’s macOS 10.16, but to newly-built app it’s macOS 11.0?
Do you know how to customise the zsh shell now standard in Catalina? Here’s an excellent book which covers it in detail – and curious choice in 10.15.
The new read-only system volume changes a lot of paths on which scripts and apps rely. Here’s some experience in fixing the problems that result.
A simple command tool to write messages to the unified log in Sierra and later. Now signed, hardened and notarized.
Was WWDC a damp squib after all? With only one new unaffordable Mac announced, and more dreadful privacy dialogs on their way, you might think so.
Source code workthrough of one method of checking for and automatically downloading updates to an app, in Swift 5 for macOS 10.11-10.14.
How can an app check that nothing has nobbled it? How to use its code signature to perform a simple launch test.
