Driving Sideways reports:
AppleScript, in case you didn't know, is Apple's operating system scripting language. And through some mad genius science you can now create standalone applications with it through AppleScript Studio. Great! So now I can easily create an application that will automate some of my tasks. Woo hoo!
The only problem is that the AppleScript language itself, which purports to be this laymens language, is actually a convoluted painful nightmare to work with.
For example. I was stuck for an hour on a debugging statement that I had that printing the name of a file that I got from the Open File Dialog. Time after time I tried to print this thing out but I would get some impentrable "NSCouldNotCreateScript" error. What does that mean? So I Googled it and one poor bastard out in Slobovia had it once, maybe, couldn't figure out what it meant and went on. Turns out the secret ju-ju was to add 'as string' on the end of the statement.
Applescript is pure ass. No other language makes a programmer feel so stupid. And what's even more insulting is that it's supposed to be a 'for dummies' type language.
I second that. AppleScript should be the magic sauce that makes Mac OS X really shine. But every single time I've tried to integrate two apps or create some automated workflow, I have spent way too much time on mundane things. Each app has its own ideas of nouns and verbs, and I spend too much time just trying to figure out the correct object specifications.
Then again, I am disappointed when apps don't include any AppleScript, such as MacJournal. Go figure...
Recent Comments