5 ms·
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
by pmoriarty 7y ago
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 of research and effort in to creating an ecosystem around them like text-based languages do.
There's no way to grep, diff or sed the source while remaining on the visual level. There's no way to harness the incredible power of text editors like vim or emacs. When there are lots of connections, determining what's going where becomes difficult to determine, though at least they do have some modularity. Debugging and tracing facilities tend to be minimal to non-existent. There are no static analysis tools, refactoring tools, fuzzing tools, unit-testing tools, or behavior-driven testing tools, no way to design by contract.
These things are in their own little backwater. They look cool, and are easy to start with, but that's about it.
- qmmmur 7y agoThese 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 the need for functionality grows. I'd say I'm an expert in Max having spent considerable time in it developing applications and doing research and the trade off of not having those 'traditional' software engineering and computing tools is that you can work in an incredibly dirty and ad hoc way. At the end of the day it's a tool designed with creative goals in mind and the idea of unit testing, deploying, etc etc are not paramount to people's practice mostly. They just want to develop ideas fast in fairly stable real-time environment.
- jcelerier 7y ago> The point of Max is to be one notch away from something like Ableton ahaha, when you think that Ableton was born from Max :)
- whiddershins 7y agoThat doesn’t sound right.
- pmoriarty 7y agoThis 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.
- TheOtherHobbes 7y agoThe lack of tools isn't the problem. The problem is that Max reimplements basic CS concepts badly, eccentrically, and unintuitively, for no real benefit, while adding a huge extra cognitive load. Max for Live highlights why this is bad. If you can find the unofficial docs, it's much easier to access the LOM using Python - or pretty much any standard language - than to do all the string/list/symbol splitting, prepending, filtering, combining, and so on you're forced to do to make anything non-trivial happen in Max itself. I think there's an open niche between Max, which is just plain weird and difficult in too many ways, and the low-level world of Juce and C++. I'd love to see a scriptable industry standard plug-in architecture with a super-easy "just works" set-up for graphics, DSP, MIDI and timing, based on a modern high-level language, but also fast. WebAudio is somewhere in that niche, but - aside from being browser dependent - it's still too close to the metal for most users. Some of the plug-in construction kits are too high level. Faust is good but still very specialised. I suspect there's a sweet spot between the extremes, and it's not currently been catered to.
- qmmmur 7y agoAgain, you're missing the point. Max and pd were developed for composers and musicians to execute live performances of institutionalised academic music (as well as its long history of connections to IRCAM in Paris). It does that perfectly.
- aikah 7y agoReaktor does it better and is simpler to learn in my opinion. Max tries to be both high level and low level, which makes it more a tool for engineers than artists.
- jcelerier 7y ago> Languages like these also don't have the almost hundred years of research and effort in to creating an ecosystem around them like text-based languages do. c'mon, the first dataflow languages date from the 60s, that's barely after the first textual PLs - see eg https://www.youtube.com/watch?v=QQhVQ1UG6aM https://www.youtube.com/watch?v=QQhVQ1UG6aM > There's no way to harness the incredible power of text editors like vim or emacs. have fun showing most art students how to use vim or emacs :p just typing a few commands in a console to build a project is already a galore from past teaching experience.
- dhosek 7y ago> have fun showing most art students how to use vim or emacs :p just typing a few commands in a console to build a project is already a galore from past teaching experience. Back in the 80s, I used to teach LaTeX workshops, primarily to math department secretaries. These were usually given in a university's computer lab. At one such lab, the staff had decided that the students should use vi. The problem was that the terminals were such that hitting any of the arrow keys would be interpreted by vi as delete the current paragraph irrevocably. After one morning of frustrated students, I switched everyone to emacs. We didn't use a fraction of emacs's power, but at least the arrow keys worked.
- DonHopkins 7y agoThanks for that link to the wonderful video of Alan Kay showing a demo of GRaIL recorded in 1968! Here's a film of another early system called "PIXIE" for editing graphs and circuit diagrams by Neil Wiseman, Lemke and Hiles from 1969, showing the first know implementation of what I call "pie menus". The librarian David Chapman at the Cambridge University was quite helpful and generous enough to arrange for that film to be transferred to video and posted on their site. (Librarians rock, and Cambridge University has an excellent library! ;) It hasn't widely seen, and was only recently published online! https://www.cl.cam.ac.uk/library/archives.html https://www.cl.cam.ac.uk/library/archives.html >This film demonstrates an early graphical user interface in use. It was made in 1969 to accompany a paper entitled “PIXIE: a new approach to graphical man-machine communication” presented at the 1969 CAD Conference held in Southampton. https://medium.com/@donhopkins/pie-menus-936fed383ff1#8546 https://medium.com/@donhopkins/pie-menus-936fed383ff1#8546 >History of Pie Menus >The classic 1969 “PIXIE” paper by Neil Wiseman, Lemke, and Hiles had the first mention of circular menus, which was referenced in Newman and Sproull’s 1979 seminal book “Principles of Interactive Computer Graphics”. The “lightbuttons” were apparently target area based (selected “by pointing at one of them”), unlike pie menus which are based purely on the direction of the gesture, resulting in a large wedge shaped target area extending to the screen edge, not just the small rectangular area of the “lightbutton” label: >PIXIE: A New Approach to Graphical Man-Machine Communication >Wiseman, N.E., Lemke, H.U. & Hiles, J.O. (1969) PIXIE: A New Approach to Graphical Man-Machine Communication, Proceedings of 1969 CAD Conference Southampton, IEEE Conference Publication 51, 463–471. >"The control lightbuttons which are used frequently within a mode to carry out a sequence of operations. These buttons are displayed around the tracking cross and move about with it so that the user’s hand is always close to these buttons when he needs them. To avoid clustering a large number of control buttons around the tracking cross, it is arranged that only buttons for those actions which are legal at any given time are displayed and also that the user may select different sets of legal buttons by pointing at one of them (which acts as a sort of rotating switch for the rest)."
- pjmlp 7y agoSome of those chaos just happens, because just like in textual languages, many people write monoliths instead of making use of the modular tools made available to them. Most visual languages that aren't toys, do have search capabilities, visual debuggers, and most importantly the ability to package code blocks into modular units. Unreal's Blueprint tooling is quite powerful, and several games have been written like 99% in Blueprint.
- deleted 7y ago[deleted]