Skip to main content
Ask Different

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

Since Yosemite, OS X/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

One advantage is that there are many more editors and IDEs out there designed for JavaScript coding than there are for AppleScript, though Script Editor and Automator probably still have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

Since Yosemite, OS X/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

One advantage is that there are many more editors and IDEs out there designed for JavaScript coding than there are for AppleScript, though Script Editor and Automator probably still have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

Since Yosemite, OS X/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

One advantage is that there are many more editors and IDEs out there designed for JavaScript coding than there are for AppleScript, though Script Editor and Automator probably still have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

spelling
Source Link
oa-
oa-
  • 7.8k
  • 5
  • 24
  • 45

Since Yosemite, OSXOS X/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

One advantage is that there are many more editors and IDEs out there designed for JavaScript coding than there are for AppleScript, though Script Editor and Automator probably still have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

Since Yosemite, OSX/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

One advantage is that there are many more editors and IDEs out there designed for JavaScript coding than there are for AppleScript, though Script Editor and Automator probably still have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

Since Yosemite, OS X/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

One advantage is that there are many more editors and IDEs out there designed for JavaScript coding than there are for AppleScript, though Script Editor and Automator probably still have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

added 46 characters in body
Source Link
calum_b
calum_b
  • 6k
  • 30
  • 37

Since Yosemite, OSX/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

Of course, withOne advantage is that there are many more editors and IDEs out there designed for JavaScript you can use any code editor you likecoding than there are for AppleScript, though Script Editor and indeed Automator offer some debugging options that 3rd party editors probably won't give youstill have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

Since Yosemite, OSX/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

Of course, with JavaScript you can use any code editor you like, though Script Editor and indeed Automator offer some debugging options that 3rd party editors probably won't give you.

Official resources:

Some unofficial resources:

Since Yosemite, OSX/macOS also supports JavaScript as an inter-process scripting language--officially known as JavaScript for Automation, also referred to as JXA. The documentation (and some would say, the implementation) is somewhat lacking compared to AppleScript, but if you're already more familiar with JavaScript than AppleScript, then it might be an option.

Like AppleScript, JXA also offers an ObjC bridge allowing you to use Cocoa APIs in your JavaScript.

One advantage is that there are many more editors and IDEs out there designed for JavaScript coding than there are for AppleScript, though Script Editor and Automator probably still have the edge for debugging JXA-specific stuff.

Official resources:

Some unofficial resources:

added 6 characters in body
Source Link
calum_b
calum_b
  • 6k
  • 30
  • 37
added 104 characters in body
Source Link
calum_b
calum_b
  • 6k
  • 30
  • 37
added 16 characters in body
Source Link
calum_b
calum_b
  • 6k
  • 30
  • 37
Source Link
calum_b
calum_b
  • 6k
  • 30
  • 37