We reviewed the topic.
The storytelling now goes like this:
VVVV is unmatched in its combination of
- letting you express yourself in a language that detects typing errors early and thus is able to guide you with typing errors on links and data hubs, while
- still letting you iterate fast by being able to test those parts of your program, that don’t have a problem
So that’s our insight: You want the errors in order to be able to track down potential bugs early, but you also want to be able to work and test refactored versions of your patches before solving each and every single issue.
But you are completely right, that red node applications and red node definitions all over the place are not helping when it’s about
- finding the actual issue
- estimating the real amount of problematic patches
We, therefore, now mark patches as red if they contain errors. They still partly run. But to find the error we figured you want those nodes to show up in red. All the others, that are further away from the initial issue - nodes that only use nodes that have errors inside - are now considered as worth having a look at. Thus we put a warning on them (making them orange).
From a definition perspective, we mark Categories in red that contain red definitions.