3 ms·
Hey this looks really sharp. It seems a bit like Processing but for .NET, is that a fair characterization and if not how would you say your project differs? (
by stallmanite 7y ago
Hey this looks really sharp. It seems a bit like Processing but for .NET, is that a fair characterization and if not how would you say your project differs? (Asking only for elucidation and to maybe stimulate some discussion on the thread, definitely not commenting in the vein of “Processing does this so what’s the point”. A world with more tools like this is a good thing.)
- discreteevent 7y agoI don't think processing has anything to do with visual programming.
- joreg 7y agoRight, the most obvious difference is that vvvv is visual. Then comes the "live-programming" aspect which means that in vvvv you don't "edit-compile-fixcompiletimeerror-compile-run" but you always only run and modify the running program. Compilation happens in the background. If there is a compile-time error, vvvv points that out for you, but keeps running. runtime-errors also don't necessarily completely stop the program. So while in the end you can certainly achieve the same things with vvvv and processing, the way you do things is very different.