When humans explain how to tackle a Mac problem, they usually prefer to use GUI apps when appropriate. AI much prefers you to enter commands into Terminal. This has consequences.
command
How the keyboard can be used for commands, from its reserved keys, to key equivalents, interface controls, and keyboard actions.
App signatures remain valid forever, but Installer packages are different, and their certificates can and do expire. What about notarization though?
Although there doesn’t appear to be any straightforward way to run command tools or scripts only on Efficiency cores, there are ways and means.
How can you create and resolve Finder Aliases at the command line? And two further utilities you may find helpful for working with Aliases.
How you can write entries in the unified log which are informative, easily retrieved, and extremely simple.
Discovering what has been updated in a macOS update isn’t easy. In the case of command tools, it’s just impossible.
Do you use third-party command tools? Are you using or planning to use Catalina? This explains how 10.15 changes first run checks on those tools, and their effect on all users.
Downloading runtime support from Apple can save you wondering why a tool appears to be broken.
Calling command tools from Swift changes with macOS 10.13 and 10.14 with the deprecation of some of the Process class. Solutions aren’t as clean as they should be.
The Eclectic Light Company 