When releasing iWork 2013, Apple ditched all AppleScript bindings[1]. In later updates, the bindings returned[2], but it still caused uncertainty about the futu

When releasing iWork 2013, Apple ditched all AppleScript bindings[1]. In later updates, the bindings returned[2], but it still caused uncertainty about the future for users with AppleScript workflows. Something similar happened when they released Final Cut Pro X[3], also fixed in later updates. But again: uncertainty, and many users prematurely switching to alternatives (like Adobe Premiere). [1] http://www.macworld.com/article/2058705/the-state-of-applescript-lets-not-panic-yet.html http://www.macworld.com/article/2058705/the-state-of-applesc... [2] http://www.macworld.com/article/2090831/applescript-makes-a-comeback-in-numbers.html http://www.macworld.com/article/2090831/applescript-makes-a-... [3] http://en.wikipedia.org/wiki/Final_Cut_Pro_X#Reception http://en.wikipedia.org/wiki/Final_Cut_Pro_X#Reception