JavaScript as an alternative to AppleScript on OS X Yosemite
11–20 of 126 posts
Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#12The functionality exposed by OSX apps via AppleScript is often incredible, but the language itself is annoying.
The question is whether or not applications will support it. With the emphasis shifting away from OSX desktop applications to cross-platform and cloud apps, will OSX app developers still take the time to expose scripting functionality?
Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#13Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#14AppleScript contains some amazingly powerful APIs, but is nearly impossible to write. Having a Javascript (successor?) implementation is going to unleash its full potential. I could see it becoming much more widely used and supported by third party apps. This is wonderful. In the same cycle that they release a brand new language, they begin the deprecation process for their (only?) other proprietary programming langu…
Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#15[deleted]
Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#16Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#17Haven't wrapped my brain completely around this yet, but I wonder if it's going to allow for some cool (and/or dangerous?) crossover write-once-run-in-browser-or-locally apps.
You don't write applications in AppleScript; you use AppleScript to control other applications in an automated way.
You can write AppleScripts with simple dialog boxes and such, just as you can write interactive bash scripts. And while you could theoretically implement an application entirely as a shell script or batch file or AppleScript, it'd be a bit like mowing your lawn with a pair of scissors.
Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#18[deleted]
Re: JavaScript as an alternative to AppleScript on OS X Yosemite
#19This makes me really happy. I kind've wish they'd used $ for what Application() is, though, to keep an analogous similarity with jQuery and the like.
(Although, I suppose, you could use another var for jQuery, such as, uh, 'jQuery' ...)