Hacker News Reader

Comment by tuananh | Hacker News Reader

what is the meaning of "node-based" here?

Look at the screenshots in the repo - it refers to applying or stacking effects/edits based on a system of linked nodes, as used by color grading software such as Davinci Resolve, and also used by Blender I believe.

Which iirc, is contextually referred to as visual programming. Some notable examples I've briefly used include: PureData [0] and SunVox [1] and some dabbling in Bespoke Synth [2] and generative content of Nodes.io [3].

[0] https://puredata.info/

[1] https://warmplace.ru/soft/sunvox/

[2] https://www.bespokesynth.com/

[3] https://nodes.io/story/

Somewhat. This is true for the drag-and-drop interface and representation, but nodes here are an implementation detail IMO. Nodes are a subset of visual programming, and well-suited for representing functional and data-oriented processing pipelines.

In turn, these programming paradigms are well suited to hardware acceleration and distributed/multithreaded pipelines.

The underlying edition approach is called "non-destructive editing", as you can always remove some operations to find the original again.

When it comes to visual programming, the first example that comes to my mind is labview, which I find very unwieldy to work with. As a programmer, node editors are one of the very few visual programming methods I'm comfortable using (at least as long as the graphs stay relatively small).

I always found these editors to be a bit more cumbersome than just writing things in code. I do like the visual feedback in form of previews. Perhaps the optimal workflow would be a code-based editor with easy visualization of each stage, notebook style perhaps?

The way in which the effects are specified/applied

Photoshop/GIMP would be "layer-based"

Reply on news.ycombinator.com