The survey offers the following choices for each of the scripting languages:
• Critical to my work • This language is nice to have, but I could do without it if I have to • This language isn't important to me • I've never used this language and probably never will • No answer
It then asks how the scripts are used: whether sold to end-users, developed in-house, offered as a value-add by an integrator, or written on a contract basis for a customer.
Now, there's an "Other" field. If they were asked, this might be the place that would be filled in by the many thousands of individual Mac users who take advantage of AppleEvents scripting to automate their workflows. But these folks aren't the target demographic.
It's easy to read between the lines here: if we're counting the votes from professional scripters, and considering a product that supports multiple platforms, which is made at a company that is pitching its own framework, AppleScript may be running out of luck.
Comments to his suggestion appeared to fall into two camps: those who hate AppleScript, and those programmers who started out with AppleScript and graduated to other languages (or still stick with it).
I appreciated the thoughtful response from some of the latter camp.
For example, Kevin Walzer said that professional programmers underestimate how user-friendly it can be for beginners. He was responding to post that said that while AppleScript code can be easy to read, it wasn't easy to actually code.
After years of more powerful languages likeTcl and Python, of course, my own perspective on AppleScript has changed to a degree; its quirks are more annoying, and I still have to refer to Matt’s book on occasion. I just got hung up writing an AppleScript that accessed a single-item list, and it took me forever to translate “theList” into AppleScript’s “item 1 of theList”.
He said that AppleScript was still part of his toolbox. "It is the quickest way to access certain resources in OS X. ... Apple has enabled AppleScript to fit in comfortably with other scripting languages."
Yes, programmers - who make their living as programmers - may not like AS, and may prefer JS. But that’s not who AS is aimed at; and the latter group is much, much bigger and could benefit *so* much more from even a little automation in their lives. Making them do Olympic high jumps just to get over a low fence doesn’t seem right.
Still, programmer Bob Warwick wasn't buying it. He said that Automator should now be the scripting solution for novices.
Since the introduction of Automator, I think that argument loses all water. That’s the real scripting language for never-programmers on the Mac.
There are serious workflows in large companies based on AppleScript. But its longterm usefulness may be in question. Or not. What do you think? Are you a scriptor or an AppleScriptor?