I have a real problem with visual languages like Max and PureData (and all the other visual languages I've ever seen). They seem like a good idea, and might be fine for computer-phobic people just starting to be introduced to programming, but whenever one tries to make anything even a little complex in them they inevitably become a mess of spaghetti-code. Languages like these also don't have the almost hundred years…
These are valid criticisms (although parsing max patches is very easy as they are just json files). However, I think you're missing the point. The point of Max is to be one notch away from something like Ableton - a language and methodology for programming your own routines, patterns and at the lowesr level DSP algorithms (something that gen~ has facilitated nicely). You might even write your own objects in c++ if th…
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.