Developer Jonathan “Wolf” Rentzsch kicked off his annual C4 indie Mac developer conference in Chicago on Friday night with a provocative claim cribbed from Steve Jobs: He showed a slide of the AppleScript logo in a coffin and declared it dead.
I will admit that I’m deeply skeptical of the entire suggestion, not because I think AppleScript is a great language—though I use AppleScript every day, I am painfully aware of how difficult it can be to use—but because I’m concerned that programmers might not truly grasp that their customers aren’t as comfortable writing complex syntax full of brackets and semicolons as they are.
I talked to a bunch of developers after Rentzsch’s presentation, and it was interesting to get their perspectives on this topic. One message was clear: implementing AppleScript support can be really hard. But as one developer told me, “Yeah, implementing AppleScript is hard. You should do it anyway.”
The big questions to me are: Who exactly uses scripting? And what are the best tools for those people?
I’m struck by a comment made on Daniel Jalkut’s Red Sweater Blog about this topic earlier this year. “JSTalk is very much by a programmer, for programmers… AppleScript is for normal people,” the commenter wrote. I’m not sure I’d classify AppleScript users as entirely normal, but the larger point stands: people who are not computer programmers but who are power users need some way to control their applications and, most importantly, use scripts to weld disparate applications together in order to save time and improve productivity.
I’m not convinced that Rentzsch’s suggestion that we bury AppleScript and replace it with JSTalk is a good idea, but I do think the conversation is worth having. Scripting might not be a feature used by most users, but I know that my Mac life would be much less productive if I didn’t have access to the slew of scripts I use every day.