[PS Scripting] ExtendScript support for ECMAScript 6th version

  • 38
  • Idea
  • Updated 2 years ago
ExtendScript as it's implemented in Photoshop Scripting engine is compliant to:

- ECMA-262 (version 3)
- EX4 (EcmaScript for XML)

plus other custom stuff like Filesystem management, Reflection interface, operator overloading, etc.
It's a great language, but... the rest of the Javascript world has moved to ECMA-262 version 6 aka ES6 Harmony, while so to speak we're stuck at ES3.

We don't have native support (among the rest) of JSON, Array.indexOf, Promises, Object.create, etc...

It's becoming increasingly difficult to interface with JS libraries, since shims are not always available/functional.

Also, strategically, we're in a cul-de-sac (aka dead end): there hasn't ever been a major language update (besides ScriptUI changes to support different rendering engines over the years), the PS Scripting language cannot not-evolve now that JS seems to have gained a great momentum and it's as lively as it's never been in the past.

My feature request is not to substitute ExtendScript with JS tout-court (since it would mean give up to EX4 and proprietary stuff), but to incorporate the new ES6 syntax and features - give ExtendScript a place in the future.

Thank you very much,

Davide Barranca
---
www.davidebarranca.com
www.cs-extensions.com
Photo of Davide Barranca

Davide Barranca

  • 21 Posts
  • 3 Reply Likes

Posted 3 years ago

  • 38
Photo of Constantin Cerdan

Constantin Cerdan

  • 1 Post
  • 0 Reply Likes
I completely agree with Davide. Please add support for this!
Photo of Shawn Flanagan

Shawn Flanagan

  • 1 Post
  • 0 Reply Likes
ES6 would be super useful in PS for us script/extension writers. Please help us make your product better for the users!
Photo of MonkeyMe

MonkeyMe

  • 2 Posts
  • 1 Reply Like
Unfortunately I don't have the faintest idea what this is all about since I stopped programming a decade ago. But I know Davide and everything he does is truly reasonable.
Photo of Davide Barranca

Davide Barranca

  • 21 Posts
  • 3 Reply Likes
:-) Thank you, from now on I'll ask my wife to call me Davide "reasonable" Barranca!
Photo of giuliana abbiati

giuliana abbiati

  • 2 Posts
  • 0 Reply Likes
+1
Photo of Davide Barranca

Davide Barranca

  • 21 Posts
  • 3 Reply Likes
My mistake, I should have written 'E4X' (ECMA357) - thanks to @indiscripts for reporting!
Photo of Pedro Marques

Pedro Marques

  • 161 Posts
  • 25 Reply Likes
I do need this for our workflow optimization!
Photo of Daniele Di Stanio

Daniele Di Stanio

  • 1 Post
  • 0 Reply Likes
Davide' extensions are critical for mine, and my clients, workflows, I'd love for him to have the widest toolset possible for his work, thanks Davide.
Photo of Matias Kiviniemi

Matias Kiviniemi

  • 8 Posts
  • 0 Reply Likes
Thumbs up, it's very frustrating having to "cut back" on what you know and like is the best way to code JS because it'll not work with ESTK. We have regularly updated Chrome in panels and modern Node.js in Generator, but ESTK is holding all those back.
Photo of Sergey Kritskiy

Sergey Kritskiy

  • 46 Posts
  • 20 Reply Likes
Totally agree! I want .forEach() and .map()!
Photo of Max Johnson

Max Johnson, Champion

  • 434 Posts
  • 202 Reply Likes
Having to play the "is this basic native function supported or not" game is not a fun one. Having to write and/or include my own versions of things like Array.firstIndexOf() is frustrating.
Photo of Robert

Robert

  • 4 Posts
  • 0 Reply Likes
I support this request! 
An update with ECMAScript 6 features would allow to code cleaner, better, faster, stronger.
Photo of Oliver Zabraczky

Oliver Zabraczky

  • 1 Post
  • 0 Reply Likes
Voted! Beside this the ToolVM javaScript engine is extremely slow compared to PanelVM's.
Photo of Javier Aroche

Javier Aroche

  • 2 Posts
  • 0 Reply Likes
+1

ExtendScript needs some love! Otherwise a lot of our work will become useless very soon.
Photo of Remco Janssen

Remco Janssen

  • 3 Posts
  • 0 Reply Likes