Max 8 JS question for devs

    Apr 21 2018 | 5:16 pm
    So, this is exciting news for Max 8, adding Node integration:
    Does this mean that Max's Javascript engine will be updated to support ECMA Script 6 features?
    The last word I found on the subject from the Cycling '74 devs was here:
    Where Joshua said:
    The implementation that integrates completely with Max is based on the spidermonkey engine (and specifically the jaegermonkey JIT compiling version) and corresponds to Mozilla's Javascript 1.8.5 (which is a relatively modern ES 5+ version). There are no plans to update this to more modern engines in the near future, as it represents a significant amount of engineering to do so.
    That was from a couple years ago. So I wonder if now Max will be adopting the Google V8 Javascript engine instead, which is what Node is built on. That would be great for the future of using Javascript in Max. I've lately been using a ton of it, and it's already powerful.

    • May 25 2018 | 3:52 pm
      Bump... devs, any hint?
      In short: in Max 8, will Max's Javascript engine be updated to support ECMAScript 6 features?
    • May 25 2018 | 6:11 pm
      Joshua's answer in that thread remains definitive on the subject of Max's internal JS engine (which is distinct from the node in max technology).
    • May 25 2018 | 10:21 pm
      So Max is going to be running 2 independent Javascript engines simultaneously? Ok, that’s not what I expected... guess I’ll have to wait and see what kind of patch integration the node.script object offers.
      Thanks for the clarification.
    • May 26 2018 | 1:12 am
      While I hope that Max's internal JS engine is updated I also I certainly hope that node for Max will have the same integration with Max and Live Api that the js object does - although I presume so, because otherwise there wouldn't be a whole lot of benefit from node in Max over outside of Max via [udpreceive] or some other communication protocol.
    • May 26 2018 | 12:01 pm
      any chance to get a early copy of the node.script object? I'm just working on a project which uses MagentaMusic.js npm package, so I'd like to evaluate if the new object would be the right way to integrate it.