| Hey, edmund, I feel your pain, but Cocoa APIs that only an eye-blink ago were but babes-in-arms have been brought into this world, momentarily bathed in the warmth of Cupertino’s sun, and then snuffed out with callous indifference much like (how did Rutger Hauer put it…) "teardrops lost in the rain".
Point being: AppleScript scripts probably have the second longest longevity in Apple’s ecosystem right after shell scripts.
I hear ya on wanting something better. I just think we can probably all pull in the same direction to better effect.
Best
Phil
On 21 Nov 2016, at 23:40, edmund ronald < email@hidden> wrote:
I have a two line applescript that got broken with Sierra, thevsemantic changes are huge- suddenly it's executing from a temp read only directory. AFAIK legacy shell scripts that are 30 years old still run on these machines, untouched. Home automation won't be very helpful if your house heating gets broken by a script change - this thing is a pig, and it is time we as developers got a better tool. On Monday, November 21, 2016, 2551phil < email@hidden> wrote:
On 21 Nov 2016, at 23:05, edmund ronald < email@hidden> wrote:
I'm not signing this - I WANT AUTOMATION, MODERN AUTOMATION, NOT THIS LEGACY PIG.
Block caps…you must be serious!
Meanwhile, not that I’m evangelising for that petition in particular, but exactly how does supporting that harm your quest? Are they mutually exclusive? Isn’t it possible that if Apple see 146!! people crying over spilt AppleScript milk they might just go, “you know that SwiftAutomation thing someone keeps harping on about? Maybe it might be worthwhile stuffing that in instead of that legacy pig?”
Point being: we can all be on the same side in this. Just a thought.
Best
Phil
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden
|