3 ms·
The problem with AppleScript isn't the verbosity, it's the fact that the verbosity hides the API path model, which is actually quite brittle, obscure, and poorl
by TheOtherHobbes 6y ago
The problem with AppleScript isn't the verbosity, it's the fact that the verbosity hides the API path model, which is actually quite brittle, obscure, and poorly documented - possibly because the features were added as an afterthought to the Accessibility framework, and there is no actual Automation API.
You spend a lot of time selecting objects or processes, and the syntax can appear painfully arbitrary with a lot of "Need to know the magic word" code that you can't improvise from scratch - because you don't know the magic word.
The fix would be to expose the API so users can click on any on-screen object, and AppleScript fills in the API path for the object.
There's a utility that sort-of does this, but it's very well-hidden and not at all easy to use.