ExtendScript Bugs? (proper language guide for ES)

[Invitado]

We've come across some differences in behavior between PS's ExtendScript and actual JS.  The most recent example involves logical expressions:

 1 && 2 || 3 && 4 // (4 in Photoshop and 2 in Chrome/IE/Safari/NodeJS)

Are these behavioral differences bugs or "features"? If it is intended to deviate from JS, is there any sort of proper ExtendScript language reference that documents the issues?

P.S.: If any Adobe employee reads this, would it be possible to just integrate V8 or a more modern JS engine?

[Jarda Bereza · Accepted solution]

Somebody already had same question. But there was not usefull answer.

Some anomalies are here: PS-SCRIPTS.COM - Bugs, Anomalies, Documentation Errors

But it's not official documentation.

The JSX has some extra features like writing/reading disk.

In HTML panel you could use ECMA6 and node.js

There is Blink engine like in Chrome. But you still need to use some JSX.

[Invitado]

@Jarda_Bereza Thanks for the reference! We will definitely search the ps-scripts forum next time we come across an issue.

@Tom_Ruark Even if switching to a modern JS engine is not feasible, some Adobe-blessed ESLint rules would help JS developers ensure code will work in ExtendScript.  Most of the quirks we came across are parsing discrepancies and it should theoretically be possible to detect bad patterns with static analysis.

[Jarda Bereza]

Adobe maintain Action Manager code and DOM code a little bit. They do some documentations updates sometimes. And I appreciate it. But core of JSX and ExtendScript toolkit seems to be untouched for years.

Anyway if you open folder: c:\Program Files (x86)\Adobe\Adobe ExtendScript Toolkit CC\Required\

there are many .jsx files with aplication logic. So we maybe could adjust ExtendScript Toolkit to fit our needs.

[Tom Ruark]

We had a person that was going to move to V8 from ExtendScript over the weekend. They didn't come back yet from their weekend.

[xbytor2]

To whom should I send the flowers?