4 ms·
There's the usual scaling problem with graphical representations. The now-discontinued Blender game engine was an example of building a complex system by conne
by Animats 6y ago
There's the usual scaling problem with graphical representations.
The now-discontinued Blender game engine was an example of building a complex system by connecting up boxed with arrows. You could easily get to a few square meters of program, and then finding anything was tough.
Dynamicland PR: "Programs are flexible, and compose readily." So what do you compose? A functional block with ins and outs? What's the equivalent of a subroutine? That's where graphical systems usually fall down.
- myhf 6y agoThere are some interesting examples of large visual programs at https://blueprintsfromhell.tumblr.com/ https://blueprintsfromhell.tumblr.com/ I think the goal of Dynamicland is to build computational paradigms other than procedure-oriented programming. Individual cards can call lua subroutines, but the emergent behavior between cards is not the same type of composition as connecting subroutines. It reminds me of the gameplay in "Baba is You": the "program" is the set of rules currently in play, and the emergent behavior is the set of moves allowed by those rules.
- Animats 6y agoThere are some interesting examples of large visual programs at https://blueprintsfromhell.tumblr.com/ https://blueprintsfromhell.tumblr.com/ Yes, same problem, and same solution, as the Blender game engine. ROS, the Robot Operating System, which is really a message passing library that runs on Linux, is something like that, too, with blocks connected by one-way connections. Emergent behavior between cards is not the same type of composition as connecting subroutines. Good point. You can start to see where this model works. Things where there's a lot going on in parallel, and loosely coupled modules need some interconnection. People keep re-inventing this idea, but so far, it tends to get really messy as it scales up. There's a second level of concepts needed here, something comparable to the invention of modules or classes or traits in programming.
- robenkleene 6y ago> So what do you compose? A functional block with ins and outs? What's the equivalent of a subroutine? That's where graphical systems usually fall down. Most visual programming languages have nodes with ins and outs that contain other nodes, just like you’re suggesting. And yes, I’d consider them the equivalent of subroutines. Programmers seem to talk about visual programming languages as if they’ve failed, but outside of software engineering they appear to me to be more popular than text-based languages. Some examples are VFX, compositing, audio/MIDI, prototyping, and automation. My own working hypothesis is that plain-text based version control is why most software engineering uses text files. The big differentiator between software engineering and other fields is there’s very little collaboration with visual programming language projects, they’re almost always made by one person.
- munk-a 6y agoI think version control is a decent reason, but it's more the full ecosystem. As an example, how can I grep a set of visual functions for some specific pattern - what even is a meaningful pattern to look for. That lack of an ecosystem makes most devs nervous and we tend to be (rightfully) distrustful of all-in-one ecosystems since your program (probably your livelihood) is then tied to the continued support of that ecosystem. It's one reason this movement is interesting to me, if we can establish a common communication medium, specifically a non-proprietary one, then tool builders can come along and start building out that ecosystem - likely as inefficient hacks initially but ones that can be refined as the platform gets more focus.
- mypalmike 6y agoI don't think version control has anything to do with it. If there were a highly compelling and productive general purpose visual language, storing the data as text, and even providing tools to aid in things like merge conflicts, would be minor details. But when you actually dig into things like (the excellent) Prograph and its descendents, you find out that shapes and lines are actually less intuitive than text for nontrivial code bases. Contrary to what one might expect, a picture is not worth a thousand words. Perhaps a new visual paradigm will be introduced that changes things, but there's really nothing today that competes with even your least favorite popular text based language.
- gfxgirl 6y agoUnless something has changed that's some PR hyperbole. The DynamicLand I experienced was a piece of paper represented a function written in a text based programming language. You could choose to have inputs and outputs based on proximity but you didn't really "code" using the blocks. You "code" using a text based programming language. The sheet of paper shows the output of its text based code. If you want to edit that code, you grab keyboard and point it at that sheet and then you can toggle between showing the text based code or showing its output projected on the sheet. I didn't see many examples that composed all that well. I saw a few like there was a plant->bunny->wolf simulation. Plants spawn randomly, bunnies eat plants, wolves eat bunnies. So that was written in a text based programming language represented by one sheet of paper. Another sheet of paper had text based code that would graph a value over time. If you pointed its input at the sim it would show a graph of plant population, or bunny population, or wolf population. I don't remember how you chose which output to graph. It might have been based on which edge of the sim paper you connected to. Another sheet of paper had text based code that would output a value based on its orientation and draw that value on the sheet. In other words it implemented a knob. Lines were coming out of the simulation sheet so if you put the knob so the line from the simulation sheet touched the knob sheet the knob would adjust some parameter of the simulation like plant spawn rate or wolf running speed. But you can quickly see if you wanted to be able to adjust 5 parameters (plant birth rate, bunny spawn rate, bunny reproduction rate, bunny speed, wolf spawn rate, wolf speed) and you wanted to graph the populations of all 3 types you'd quickly run out of space. Further, writing anything more complex than simple programs you could write in 30 minutes seemed problematic. In other words, as a learning environment or a toy it was super interesting but at the time they were pitching this not as an educational thing but as an experiment in "computable surfaces" but it was hard to see it as more than something you bring kids to on a field trip and one or two experiences is the end of it. They said that this particular implementation (paper, projectors) was also not the end goal. You can imagine doing the entire thing with AR glasses (so no projectors needed)
- disqard 6y agoThanks for writing this up. I'm always interested in new approaches to visual programming, that move away from text -- your comment tells me that DynamicLand is still firmly anchored in text-based territory.
- caseymarquis 6y agoYou could say similar things about digital spreadsheets. They may not be a game changer for software developers, but they have an order of magnitude more users than all general purpose programming languages combined.
- CyberDildonics 6y agoThere are plenty of node interfaces that work well, but it will never work to have everything sprawled out in one space. In houdini and touchdesigner you can just press 'g' to group nodes automatically. The group is given an automatic name by default and you can reference the nodes inside with unix style paths -> /group/subgroup/nodename Blender's interface problems are about their execution of them, not the fundamental ideas. Ever heard of a kitchy dive bar having the bathroom door labels on the other door with an arrow pointing to the actual door? |Men ->| _ _ |<- Women| That's a basic description of blender's interface. It's seems like a fever dream of someone who has never actually had to use it or explain it to anyone.