3 ms·
The people who think everything would be great if only we had visual dataflow programming remind me of people who get into crypto. They have mystic beliefs abou
by astrange 4y ago
The people who think everything would be great if only we had visual dataflow programming remind me of people who get into crypto. They have mystic beliefs about computers rather than being able to figure out how something will actually work.
- namuol 4y agoFrom Bret Victor: “ In his influential essay No Silver Bullet, Fred Brooks makes the case that software is inherently "invisible and unvisualizable", and points out the universal failure of so-called "visual programming" environments. I don't fault Fred Brooks for his mistake -- the visual programming that he's thinking of indeed has little to offer. But that's because it visualizes the wrong thing. Traditional visual environments visualize the code. They visualize static structure. But that's not what we need to understand. We need to understand what the code is doing. Visualize data, not code. Dynamic behavior, not static structure.” http://worrydream.com/#!/LearnableProgramming http://worrydream.com/#!/LearnableProgramming
- PaulDavisThe1st 4y agoWhen it comes to audio, most of the above is wrong (or at best, off-base). Max, PureData and now a new generation of software modular synthesis applications visualize code-that-spews-data-at-other-code. They are used to build highly modifiable (though not dynamic) structures that behave in ways that are often hard to hold in a human mind. They are widely used, much loved, and insanely powerful. They use visualization to add visual memory to the cognitive toolset in ways that textual code does not. Of course, such tools are unlikely to ever be used build such tools. You don't implement/bootstrap a visual (audio) data flow language using a visual data flow language.
- 082349872349872 4y ago> You don't implement/bootstrap a visual (audio) data flow language using a visual data flow language. I do hope someone gets nerd sniped by this challenge. Not me, but someone.
- jazzyjackson 4y agoDataflow programming works well for many a visual artist (shader graphs), musician (max/pure data) and CAD engineer (rhino's grasshopper) Grasshopper is meant to parametrically generate 3D objects but it was so good at splitting and recombining tables of data that were being continuously updated that I started using it for general purpose text manipulation. the ENIAC was a dataflow machine before it was a stored program machine btw
- astrange 4y agoIt does, but my favorite dataflow based video editor (AVISynth) is a text-based programming language with an unusual evaluation model, the programs themselves aren't visual. I guess the most popular dataflow language in the world would be Verilog? But that's not visual. I don't know much about how it works professionally though.
- jazzyjackson 4y agoNever heard of AVISynth, looks really useful thanks, I edit videos sparingly and painfully with ffmpeg It's a good distinction to draw, that dataflow is separate from the editor interface. I suppose Excel is a visual dataflow editor as well.
- djmips 4y agoI've never used Verilog but was curious about it and now that you mention it's a non visual dataflow language, a lightbulb went off. Thanks a million. That implies that somebody somewhere makes a dataflow visualizer for Verilog. I'll have to look for one.
- unconed 4y agoMost data flow programming environments cannot represent lambdas, and this is why the graphs always end up turning into spaghetti: you don't actually have tools to reduce repetition in the graph's structure, using the graph itself. They are successful in artist and music contexts because the graphs tend to be simple pipelines at heart. Having dealt with sufficiently complex grasshopper graphs, I disagree that it's good at arbitrary list processing, certainly compared to ordinary list operators and iterators in code. My conclusion is that a dataflow environment that does allow for lambdas and proper n-way forking would necessarily have to be an effect system in the FP sense. It's a data flow graph that computes its own continuation and which has no fixed or preset topology. It can rewire itself based on the data flowing through it.
- josephg 4y agoI hear the criticism, but sometimes we just can't know if an idea is useful without trying it out. And trying it out can be wildly expensive - in terms of time and money. So its kinda great when someone else does that work on behalf of everyone else. Its taken 60 years of improvements to finally build ChatGPT and Stable Diffusion. If we collectively gave up on AI years ago, we might never know that. We still don't know if VR will ever get good enough for mass market appeal. Facebook (Meta) is investing big. I hope their investment pays off, but we don't know yet! It might not work. But it might! I appreciate the risk their investors are taking. And I think the same is true for visual dataflow programming. We have no idea until someone builds it out. And if their implementation is bad, we might still not know. Any implementation might just be a bad design. Anyway, Brett Victor talks about ideas that go way beyond visual dataflow programming. There's a lot of interesting stuff in there, even if a lot of it might never come to pass.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]