4 ms·
macOS is of course a Unix so it has support for CLI automation as well, and it's pretty common for macOS-exclusive applications to implement it where appropriat
by robenkleene 3y ago
macOS is of course a Unix so it has support for CLI automation as well, and it's pretty common for macOS-exclusive applications to implement it where appropriate (e.g., https://kaleidoscope.app https://kaleidoscope.app).
It also has several other forms of automation:
1. AppleScript, which often makes it faster to implement powerful scripts than a CLI because AppleScript has objects (e.g., you can iterate through the tasks in OmniFocus for example and use AppleScript's built-in date type to modify them).
2. Automator / Shortcuts, which uses a combination of hard-coded, configurable actions (e.g., an image editor would provide an action to resize an image), and URL-based automation (tell OS to open a URL, URL is sent to a specific app based on a URL scheme, app performs an action).
3. A GUI macro utility like Keyboard Maestro
I point this out because something I see frequently from folks using other OSes is to mention some other approach is better than something unique to the Mac, but macOS usually also supports that other way of doing things. These options are usually additive.