4 ms·

>Extensions are built on the NodeJS platform, a free, open-source, cross-platform JavaScript runtime environment. I applied for a job with them and proposed th

>Extensions are built on the NodeJS platform, a free, open-source, cross-platform JavaScript runtime environment. I applied for a job with them and proposed this exact thing about 8 years ago (got auto-rejected, I would've been very happy to work on it). But I'm glad to see they finally did it.

Kye 5mo ago
You could already use Node through M4L. I'm not clear on what this adds that wasn't already possible.
- moralestapia 5mo ago
  They made extensions first class, chose JavaScript as the primary language, and chose node.js as its runtime.
  - wahnfrieden 5mo ago
    Works for all tiers too
- nopayne 5mo ago
  With M4L you need to implement your feature in a device and add it to your project. My Ableton project template has a bunch of these on my main track. With extensions you use a context menu as the entry point which will hopefully be more lightweight. Hopefully they'll expose more of the object model over time and let us trigger these via keyboard/midi shortcuts.
- coldtea 5mo ago
  M4L is basically a plugin sdk. It loads as a VST would (roughly), just with access to Ableton UI elements. Ableton Extentions if a first class api to Live, kind of like AppleScript.
AaronAPU 5mo ago
I would imagine nearly every programmer who has ever used a DAW has thought “this would be cool to have its own scripting language.” They already had Python. Mentioning an architecturally obvious idea in a job application is likely to read as insulting, because it presumes their engineers weren’t already aware of that possibility.
- moralestapia 5mo ago
  I'd love to read those cover letters then. Then I can make a meaningful comparison.
- embedding-shape 5mo ago
  > Mentioning an architecturally obvious idea in a job application is likely to read as insulting, because it presumes their engineers weren’t already aware of that possibility. That's a bit much no, why would it be insulting? "Great minds think alike" would be my reaction, instead of "Ew, duh, of course we thought of that, you think we stupid?".

Kye 5mo ago

You could already use Node through M4L. I'm not clear on what this adds that wasn't already possible.

moralestapia 5mo ago
They made extensions first class, chose JavaScript as the primary language, and chose node.js as its runtime.
- wahnfrieden 5mo ago
  Works for all tiers too
nopayne 5mo ago
With M4L you need to implement your feature in a device and add it to your project. My Ableton project template has a bunch of these on my main track. With extensions you use a context menu as the entry point which will hopefully be more lightweight. Hopefully they'll expose more of the object model over time and let us trigger these via keyboard/midi shortcuts.
coldtea 5mo ago
M4L is basically a plugin sdk. It loads as a VST would (roughly), just with access to Ableton UI elements. Ableton Extentions if a first class api to Live, kind of like AppleScript.

AaronAPU 5mo ago

I would imagine nearly every programmer who has ever used a DAW has thought “this would be cool to have its own scripting language.” They already had Python. Mentioning an architecturally obvious idea in a job application is likely to read as insulting, because it presumes their engineers weren’t already aware of that possibility.

moralestapia 5mo ago
I'd love to read those cover letters then. Then I can make a meaningful comparison.
embedding-shape 5mo ago
> Mentioning an architecturally obvious idea in a job application is likely to read as insulting, because it presumes their engineers weren’t already aware of that possibility. That's a bit much no, why would it be insulting? "Great minds think alike" would be my reaction, instead of "Ew, duh, of course we thought of that, you think we stupid?".