4 ms·
It's surprising how the lazy node graph thing is spreading. I find it a superb model for most things (and, broken record moment: sidefx houdini or alias maya ca
by agumonkey 5y ago
It's surprising how the lazy node graph thing is spreading. I find it a superb model for most things (and, broken record moment: sidefx houdini or alias maya can show you how far one can go in this model. hint: james webb far).
- ReleaseCandidat 5y agoAnd 3D Compositing software like Nuke, Flame, Fusion, .... And don't forget about Blender!
- agumonkey 5y agoyeah all these compositors are from the same era.. it's funny how they all rapidly and naturally converged onto these ergonomics blender is closing in
- throw10920 5y agoWhere does the "lazy" come from? Is that just another way to say that it's a dataflow graph?
- agumonkey 5y agoyes, lazy, dataflow, reactive, I wrap all this in the same bag. Am I wrong ?
- chrisseaton 5y agoLazy is usually used to mean demand-driven, as opposed to input-driven, in my experience, so exactly the opposite of this, but different people mean different things. (Did a lot of my PhD on dataflow.)
- agumonkey 5y agoThese systems are a bit of both though. In compositing, unless you add a final "view" node, IIRC, node computations are not triggered.
- throwaway17_17 5y agoI think, as parent implied, this is more of a semantic issue than any substantial disagreement. You are, in most instances of compositing systems of this style, correct that the computations are typically not triggered unless some view node is utilized. Additionally, if your view node is in the middle of some chain of nodes, only those nodes before the view would actually be performed. This is somewhat similar to the usage of lazy in regards to the operational semantics of programming languages. Again, as parent states, lazy 'evaluation' is basically demand driven computation. Python is not a lazy language, it utilizes eager evaluation by default. So in the sense that Pyflow seems to be a sort-of 'visual programming'/dataflow frontend for Python, I would assume that it is eagerly evaluating the code in the order of dependencies as determined by the graph.
- agumonkey 5y agoI assumed pyflow nodes would be "lazish", not the code inside each node
- chrisseaton 5y agoPeople sometimes say ‘non-strict’ to mean ‘can be lazy but not required to be’. I think Haskell is actually non-strict, and not lazy, for example. It’s important because hard to optimise otherwise!
- agumonkey 5y agoand you know it got me thinking, languages are trees, and haskell tweaks it into DAG (shared call-by-need) .. evaluated one way, but in the context of UIs you get a larger graph set it seems, where any node can evolve and the consistency of the whole graph needs to be rebalanced. Just thinking out loud.
- throw10920 5y agoSorry - I didn't mean to say that you were wrong, I was just confirming if your thing with a different name than I was used to was the same as a thing in my head.
- moritonal 5y agoLazy is an odd choice of words? Lazy normally means that the data is only derived when needed, but most graph models work by pushing data wrapped as events through pipes?
- agumonkey 5y agofair point but if you only push what's changed, isn't it lazy ?
- throwaway17_17 5y ago'Push what's changed' is not a typical description of 'lazy' evaluation. As was said in a sibling comment, lazy is more of a demand-driven evaluation. However, I think you are more likely leaning into describing reactive programming paradigms. the description in parent is not exactly describing reactive, but it is certainly in the 'wheelhouse' of reactive programming. Typically, node based compositing is definitely reactive, and is most often lazy as I discuss in a sibling post.