Node graphs, pro and con


:wave: Hey, nxt dev here. We’ve definitely been wrangling with some of what @instinct-vfx refers to regarding when graphs make sense versus plain code. With nxt we’re doing our best to expose both, because every node ruins arbitrary python, we expose a node that’s designed to run another graph.

@dhruv, could you expand on the shortcomings you refer to on assuming central project and pipelines? We’d like to avoid them if you can help us understand the problem from your perspective. As of today our core graph execution relies only on python builtins and graph save files(structured json). The UI is useful for debugging and ergonomic editing, but not required to use the tool.