![]() Yes, you can use AppleScript but the thing is… AppleScript Displeases MeĪppleScript is weird. Keyboard Maestro functions as an abstraction layer for interacting with your macOS UI. APIs, resolution, window commands, all change and will break your script causing you to spend hours trying to figure out the new best way to position a window in the top right corner of your second monitor. It’s one thing to write a script that copies a file to a remote server or API, but writing scripts that automate the UI of your computer can be fraught. Like having all your code in a single repo, another benefit of having all the automation scripts in one place is that you can see very clearly where a macro could be broken apart and used as the base subroutine for several macros which allows you to create a lot less bash/javascript/clicks. It’s really helpful and allows you to share some scripts and not share others. ![]() Some folders can be set specifically for a single application, other group folders can be set to only be active on one or more computers. Keyboard Maestro gives you the ability to group macros in to folders. Having all my scripts in one place has another side benefit, which is the kismet of “Oh wait, that script I wrote for work would also work really nicely on this project too!” When all of your scripts are in one place, it’s way more likely to have those little epiphanies. Scripts are embedded in to macros, macros can be scheduled, and it all syncs via your preferred file syncing solution. Keyboard Maestro has become a single place for all macOS automation scripts to live. ![]() Unix systems, such as macOS can use cron jobs, but they don’t sync or migrate to the next computer or are simply forgotten. Even if I was diligent about keeping everything in a single directory, over time and when switching hardware, some scripts are lost, some are kept, and some are kept but the context is lost. I’ve been writing little automation scripts for decades now and they have ended up any number of places over the years, like in Documents, or ~/bin, or in Automator, or a local git repo somewhere. Here are a few reasons, and after that I’ll run through a few of my favorite automations. Yes, on it’s face it’s a drag and drop way to create automations, making it the Mac automation Swiss Army knife, but even if you can code, it is extremely valuable. Why am I writing this? It turns out that I fell in love with Keyboard Maestro. ![]() ![]() So what changed? Nothing! I can still code and I still don’t want a bunch of little specialized apps running all the time…but I have seen the light on one automation app in particular. Why? Because I can code, dammit! I don’t need a menu bar filled with little icons that are the windows to little ram-munching services when I can just write a bash script or even my own Mac app to do what I need! There are countless apps and tools and plugins and widgets for this on the Mac and over my 20 years using the Mac I have ignored all of them. You may have heard that I’ve been getting more in to automation recently, specifically automating more of my work and personal macOS environments. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |