you’ve hit a ‘bug’ in that node and @guest showcased how to extend the node with this functionality. the only issue i see here is, that there’s no possibility to contribute that 'fix/extension back to the corelib atm.
i remember a similar problem with some older filewriter node some years ago - it didn’t create a directory and in case this didn’t exist, it failed. back then we all had to wait until a devvvv fixed that node and a new beta was released.
imho VLs purpose isn’t simplifying things. i use it to push boundaries i have with vvvv in bigger/complex projects/scenarios. for example, being able to write things to disk asynchronously while some rendering is going on.
i think the real power is, that one can use it high-level, but at the same time has the ability to change a low level behaviour (like your filewriter problem) even during runtime while patching.
nope, i don’t think so, but there’s ways to make it async.
regarding the anecdote:
that’s a pity and shouldn’t happen.
but i’m not sure which node you used. i don’t have a DeleteFile in my nodelist. what i have is a Delete [IO.Path] (which also has the option to use the recycle bin which defaults to true). there’s also a Delete [VL.Lib:IO.Path] but this one is filed under external, so it might be more low-level or advanced. i just tested both nodes with empty paths as inputs and nothing gets deleted…