4 ms·
Every once in a while I think to myself, "I have a problem with OSX, I think I'll try to automate it with JavaScript for Automation (JXA)..." You know the rest.
by russellbeattie 7y ago
Every once in a while I think to myself, "I have a problem with OSX, I think I'll try to automate it with JavaScript for Automation (JXA)..." You know the rest.
The astounding lack of documentation is almost amusing. It becomes an adventure of trying to convert old AppleScript examples into JS, spelunking into GitHub and StackOverflow and general trial and error until I get something to work.
All this said, I'd rather have functionality without documentation, than the extreme of not launching an API without proper docs.
The solution of course - though Apple would never do this as it's not in their DNA - is to let devs add to their docs like PHP does. I'd be happy to add back a few examples to their site once I figured things out if that option was available to me, but right now there's really no central place for this besides random forums or starting my own repo.
- saagarjha 7y agoNobody seems to use JXA, unlike some of the technologies that are heavily used but just as undocumented :(
- russellbeattie 7y agoI don't disagree, but you might be confusing the chicken and egg. Maybe if Apple actually documented JXA... (it's actually quite useful).
- saagarjha 7y agoI know it is, but I have little hope that it ever will. Everything I've heard points towards the OSA team not doing so hot these days.