3 ms·
This kind of reinforces my point of the languages being only really suitable for simple patches, as the more complex they get the more they'll need things like
by pmoriarty 7y ago
This kind of reinforces my point of the languages being only really suitable for simple patches, as the more complex they get the more they'll need things like sophisticated debugging facilities, testing, tracing, etc to figure out what's going on, why things work the way they do or why they break when they don't.
As for them being just JSON files, that doesn't really help because these languages aren't designed to be programmed on the JSON level. They're designed to be programmed visually. Having a JSON file you can edit doesn't help any more than having an XML file of a Word document. You're not going to be editing your Word document using the raw XML. You need a word processor like Word itself or Libreoffice to make sense of it and edit it in any kind of meaningful way.
The potential is there, of course, to build text tools around manipulating the raw JSON that would be Max-aware, but that would break Max's visual paradigm and then you might as use a traditional text-oriented language to begin with.
- trynewideas 7y ago> This kind of reinforces my point of the languages being only really suitable for simple patches I can't parse whether or not this is a problem, and if so whether you're arguing that visual programming is bad or just something you don't like.
- qmmmur 7y agoIf you have Max installed I'm happy to send you incredibly complicated DSP and musical problems solved visually and cleanly. Open your mind for a second and realise that musicians needs are almost entirely different to software engineer's in a language.