This is an ok idea, but go look at the API for iPhoto, Contacts or iTunes and you'll realize it is irrelevant what scripting language is used. Really sucks that Apple doesn't open up their apps to scripting better.
Apple has its issues with scripting in its apps but other companies like Microsoft and Adobe have robust scripting support in their applications. Developers like me have created significant workflows using scripting that save my company money, time, and errors. Apps like iPhoto and iTunes are really small potatoes by comparison. Having Javascript with Cocoa for scripting is truly powerful stuff.
Adobe's scripting APIs are usually 2 versions behind in functuality and very buggy. Anyone with significant workflows that script Adobe apps got there through lots of pain and suffering.
The grass isn't always greener.
Yes, I know because I script for them all the time, but at least Adobe's API's try to be more robust than Apple's. My point was really more towards there being more to scripting than just Apple's own apps.
my experience as well; i doubt any app has such extensive scripting support as Microsoft Excel; OmniGroup's apps omnioutliner and omnigrafle also had excellent scripting support--demonstrable just by opening up an app's 'dictionary' using applescript editor (and comparing those dictionaries w/ the dictionary iphoto, itunes, etc.)
Look no further than BBEdit, which has superb scripting support and is both recordable and attachable.