3 ms·
Pretty much. Iteration and conditionals are the bane of a making a DAG elegant. I think the inverse is fairly true too, data flow is much better visualized in
by CyberDildonics 11y ago
Pretty much. Iteration and conditionals are the bane of a making a DAG elegant. I think the inverse is fairly true too, data flow is much better visualized in a DAG and much more difficult to see in an imperative line by line approach.
- agumonkey 11y agoFunny in image compositing software the iteration is abstracted away as time ticks over image sequences that update the input nodes thus pushing new outputs. It's there without being there explicitely.
- CyberDildonics 11y agoRight, and the iteration over pixels is hidden in plugins themselves. Complex filters though are difficult or impossible to build since there is no granularity and in fact gathering or scattering of arbitrary memory locations is very awkward. Anyone who has used Shake or Nuke knows that working with essentially a domain specific interface is an enormous benefit. I think there is a lot of value in learning from compositing systems as well as Houdini when writing software - namely being able to freeze data in place and iterate on one data transformation at a time.
- agumonkey 11y agoHoudini especially since he deals with any kind of data, it's almost the Lisp of computer graphics. Some tutorials are mixing geometry, analog signals (audio), discrete signals (user inputs), through Houdini's builtin operators. Never seen such versatility. I always say this should be taught in programming classes (both for UX, ergonomy, programming paradigm). And the virtual + freeze is also very present in audio production software. All this things that are close to memoization, laziness are present there.