One Apple Programmer Got Apps Talking to Each Other
Hagiographic nonsense.<p>Sal Soghoian isn’t a programmer—I’ve seen his code, it’s embarrassingly amateur.<p>Sal was <i>not</i> responsible for AppleScript of Apple event IPC; that was Cook and Harris, and that credit is theirs[1]. They walked out of Apple shortly after AppleScript 1.1 was released when Apple abruptly slashed their team. Sal had no part in its creation.<p>Sal was an enthusiastic end-user and early adopter, who talked himself into taking over what was left of that department some time later. Unfortunately, his gift for the gab was <i>not</i> matched by skills in product development and marketing. Classic case of Peter Principle in action.<p>Automator <i>was</i> Sal’s, and while it wasn’t a bad idea it failed as a popular product. It was badly positioned as a standalone app, which the standalone Script Editor already demonstrated doesn’t create interest or adoption. To sell it as an end-user solution it needed to be positioned where the end-users’ problems are: within the end-users’ apps. Automator should’ve been a self-contained GUI control for App developers to embed directly into apps, alongside the existing AppKit NSRuleControl and a standard menubar “Tasks” menu to provide high-profile visibility and instant access.<p>Soghoian’s team was also responsible for Scripting Bridge (10.5) and JavaScript for Automation (10.10), which should have won Mac Automation <i>millions</i> of enthusiastic new users amongst Python, Ruby, ObjC and JavaScript geeks, but were so technically dreadful that they even made AppleScript look good in comparison.<p>Worse, once released, Sal made zero effort to promote or support them, never mind fix their flaws; even today, a decade on, 99% of Mac programmers have no clue that these “programmer-friendly” alternatives to AppleScript exist.<p>..<p>Ironically, there <i>was</i> a true programmer-friendly alternative to AppleScript already available back in 2006: appscript[2]. I wrote appscript precisely because I was an AppleScript user who loved the automation but hated the language, and found all the other 3rd-party Apple event bridges painfully flawed. While my promotion of it was crap, programmers who used it <i>adored</i> it, because it worked <i>for</i> them and, unlike AppleScript and SB, didn’t lie or obfuscate how Apple event automation really worked. (Hint: it’s <i>not</i> OOP, it’s RPC + <i>queries</i>.)<p>Appscript was good enough that Apple even considered including it in Mac OS X… till Sal Sherlocked it with his crappy broken Scripting Bridge framework, wrecking them both.<p>..<p>As for 2014’s surprise announcement of JavaScript for Automation, that should’ve been Mac Automation’s instant salvation, launching just as interest in desktop JavaScript was taking off thanks to Node.js. Knowing its success was critical to Mac Automation’s survival, I even gave that jerk six weeks of my unpaid time to test and critique the tar out of it; even writing a JavaScript OSA reference implementation[3] for them to copy and&#x2F;or steal.<p>Halfway through Sal went radio-silent on me, which I should’ve recognized as a warning sign; but I’m a dope. Sal ignored my feedback, JXA shipped half-baked and broken, I scrapped all my plans to write the book and support its community, and Sal did bugger all to promote and support it himself. JXA sunk without trace, and Sal was still utterly clueless that he’d just killed Mac Automation and his own department as well.<p>Even then, Sal had one last chance to salvage the situation: by 2015 Swift was just about ready for production use and interest in using Swift was exploding. All Sal needed to do was hook Mac Automation onto Swift’s coattails and let Swift lift it upward for free. Seeing this opportunity coming I had already created SwiftAutomation[4] as a free, ready-made solution.<p>Alas, I made the mistake of offering SwiftAutomation to Sal—and the patronizing fool threw the offer back in my face. At which point I told him he was a arrogant incompetent unfit for the job who’d run Mac Automation into the ground. I got some bitter satisfaction when Apple sacked his useless ass not long thereafter; unfortunately, he took the whole team down with him, leaving the entire AppleScript stack parked in minimal maintenance mode and unloved disgrace.<p>..<p>And that’s Sal Soghoian’s TRUE legacy: not as the inventor of Mac Automation, but the incompetent who killed it.<p>--<p>[1] <a href="http:&#x2F;&#x2F;www.cs.utexas.edu&#x2F;~wcook&#x2F;Drafts&#x2F;2006&#x2F;ashopl.pdf" rel="nofollow">http:&#x2F;&#x2F;www.cs.utexas.edu&#x2F;~wcook&#x2F;Drafts&#x2F;2006&#x2F;ashopl.pdf</a><p>[2] <a href="http:&#x2F;&#x2F;appscript.sourceforge.net&#x2F;" rel="nofollow">http:&#x2F;&#x2F;appscript.sourceforge.net&#x2F;</a><p>[3] <a href="https:&#x2F;&#x2F;sourceforge.net&#x2F;projects&#x2F;appscript&#x2F;files&#x2F;" rel="nofollow">https:&#x2F;&#x2F;sourceforge.net&#x2F;projects&#x2F;appscript&#x2F;files&#x2F;</a><p>[4] <a href="https:&#x2F;&#x2F;hhas.bitbucket.io&#x2F;welcome.html" rel="nofollow">https:&#x2F;&#x2F;hhas.bitbucket.io&#x2F;welcome.html</a><p>--<p>Postscript:<p>For a time I did wonder if it was just me (I am am extremely prickly arse), but then I saw him pull the same arrogant condescending ungrateful crap on another experienced developer who was kindly pointing out some problems in Sal’s (JavaScript) code and offering constructive improvements. Textbook Dunning-Kruger syndrome combined with old-school Not Invented Here, and perfectly described in a great series of articles by Erik Dietrich: the “Expert Beginner”.<p><a href="https:&#x2F;&#x2F;daedtech.com&#x2F;how-developers-stop-learning-rise-of-the-expert-beginner&#x2F;" rel="nofollow">https:&#x2F;&#x2F;daedtech.com&#x2F;how-developers-stop-learning-rise-of-th...</a><p><a href="https:&#x2F;&#x2F;daedtech.com&#x2F;how-software-groups-rot-legacy-of-the-expert-beginner&#x2F;" rel="nofollow">https:&#x2F;&#x2F;daedtech.com&#x2F;how-software-groups-rot-legacy-of-the-e...</a>