There is a difference between making a DAW and publishing its complete source code, and making a DAW, whether open source or not, and making it automatable/scri

There is a difference between making a DAW and publishing its complete source code, and making a DAW, whether open source or not, and making it automatable/scriptable which is what these users seem to be looking for. Sure it’s daunting if I’m told that for some automation workflow I need to hack on some huge C++ codebase and rebuild it. Embedding a Lua interpreter or another language so one can ad-hoc control your application does not have anything to do with whether your main application is open source or not. Neovim and emacs are both open source editors, and yet they both provide a hackable interface sonyou can extend them. So does Sublime Text which is not open source. I believe that a response to “I want this stupid custom text transformation for this one project” along the lines “you have the source, implement it” is a very unhelpful one, while providing macros/scripting is the right tool for the job.