Apple dissolves Mac automation management post, Sal Soghoian to leave company
It was revealed on Wednesday that longtime Apple Product Manager of Automation Technologies Sal Soghoian, whose work is responsible for services like AppleScript and Automator, will be leaving the company in December as his post was recently eliminated.
Soghoian announced his own departure during a presentation at the MacTech Conference in Los Angeles, saying Apple is cutting the post he has held since 1997, reports The Mac Observer. Whether Soghoian's duties will be handed over to another team member is unknown, though the decision only serves to reinforce sentiment that automation technologies are no longer a priority at Apple.
The soon-to-be former employee addressed the recent development in a post to his website Mac OS X Automation.
"I joined Apple in January of 1997, almost twenty years ago, because of my profound belief that 'the power of the computer should reside in the hands of the one using it.' That credo remains my truth to this day," Soghoian writes. "Recently, I was informed that my position as Product Manager of Automation Technologies was eliminated for business reasons. Consequently, I am no longer employed by Apple Inc. But, I still believe my credo to be as true today as ever."
During his time at Apple, Soghoian worked on a variety of user automation products and technologies, many of which have seen diminished utility with each subsequent OS X -- and now macOS -- update. Apple's active automation projects include UNIX CLI (shell, python, ruby, perl), System Services, Apple Events (JavaScript, AppleScript, AppleScriptObj-C, Scripting Bridge), Automator, Apple Configurator (AppleScript, Automator), and application scripting support in Photos, iWork, Finder, Mail, and other Apple applications, according to Soghoian.
Despite Apple's decision to part ways, Soghoian remains upbeat on the future of user automation. After a brief vacation, he will begin fielding potential job offers and open himself up for consulting on Dec. 1. He also intends to maintain his Mac OS X Automation Dictation Commands websites, as well as a personal blog dedicated to his music.
Soghoian announced his own departure during a presentation at the MacTech Conference in Los Angeles, saying Apple is cutting the post he has held since 1997, reports The Mac Observer. Whether Soghoian's duties will be handed over to another team member is unknown, though the decision only serves to reinforce sentiment that automation technologies are no longer a priority at Apple.
The soon-to-be former employee addressed the recent development in a post to his website Mac OS X Automation.
"I joined Apple in January of 1997, almost twenty years ago, because of my profound belief that 'the power of the computer should reside in the hands of the one using it.' That credo remains my truth to this day," Soghoian writes. "Recently, I was informed that my position as Product Manager of Automation Technologies was eliminated for business reasons. Consequently, I am no longer employed by Apple Inc. But, I still believe my credo to be as true today as ever."
During his time at Apple, Soghoian worked on a variety of user automation products and technologies, many of which have seen diminished utility with each subsequent OS X -- and now macOS -- update. Apple's active automation projects include UNIX CLI (shell, python, ruby, perl), System Services, Apple Events (JavaScript, AppleScript, AppleScriptObj-C, Scripting Bridge), Automator, Apple Configurator (AppleScript, Automator), and application scripting support in Photos, iWork, Finder, Mail, and other Apple applications, according to Soghoian.
Despite Apple's decision to part ways, Soghoian remains upbeat on the future of user automation. After a brief vacation, he will begin fielding potential job offers and open himself up for consulting on Dec. 1. He also intends to maintain his Mac OS X Automation Dictation Commands websites, as well as a personal blog dedicated to his music.
Comments
I've sent my Feedback to Apple about this. Big mistake.
Did they part ways on unfriendly terms?
I love the Automator. It really simplified a lot of tasks, like consolidating text files, batch-renaming (which, though now build-in, still doesn't offer the flexibility of Automator+AppleScript) and adding metadata tags to music files and .cbz files.
It seemed intuitive enough for me. But then again, I was a Windows User!
If Apple someday removes Applescript and Automator I wonder if they will sell the tech to a third party so we can have continued functionality? Like people have said this has always been a nice differentiator wtih Windows. Certainly allowed me to say "Get a Mac" to people a few times as well.
Apple missed the boat by not having Automator available with an interface that could be used by someone who is the same person they've always targeted with their bundled apps, the iPhoto, iMovie, GarageBand users, aka normal people. The only people I've ever known who created a lot of useful Automations and Applescripts are people who are much more savvy than 90% of computer users and were using them for work related tasks, as firelock with his studio image work. Why did Apple never make it so that the average Joe could easily whip up a bunch of general productivity droplets for the ecosystem they created for home and non-work? It's so buried that most users never even knew it existed.
The idea was wrong, obviously, because,"natural language" and programming don't go together. Programming is "unnatural", requires a high level of abstraction not found in the natural language and cannot tolerate the looseness and fuzzy logic inherent to the natural language. Trying to "naturalize" programming resulted in a scripting system extremely complicated and difficult to use. Many of the natural language scripts wouldn't work because of the strong typing inherent to the language causing an avalanche of errors. So, the efforts to implement a system-wide scripting language was already born dead.
The mini scripting language of Filemaker Pro is the closest one to "programming for the rest of us". Scripts are built by point and click method, the system controls every step of script building process thus prevents the user from making mistakes. Automator is built upon this approach and is the first successful attempt to build a system wide scripting system. So, AppleScript may be dead but I don't think Apple will let Automator die, because it works.
The dissolution of the post doesn't imply that "automation technologies are no longer a priority at Apple". Maybe the post itself was an obstacle to the development of these technologies?
AppleScript was never really given the backing it deserved and suffered accordingly. There have been endless moments when people have moved up to new system versions and asked 'and AppleScript?' with no clear answer.
Automator has had a similar run but as it was newer you thought it had more chances of success.
If AppleScript is now dead it is a crying shame.