@ludnny What you describe is exactly the argument I wanted to pursue in the workshop `‘Programming Language vs. Authoring Environment’ .
Yet, in that sense I wouldn’t follow your line:
VL is much more of a language compared to v4, and that’s been the whole point of creating it.
V4 has the ease of use, because it is very flat, and has the ability to hold a lot of settings / data / adjustments, which makes it perfect for ‘quick n dirty’ design work.
As it stands, I don’t see how VL can hold the same amount of data without becoming totally cluttered. The fact alone that you (currently) have to create an iobox for every value that you want to set, practically renders it useless for the classic v4 usecase. And so may be the whole approach of VL - but I also see that a lot of effort is taken to bring the convenience of v4 into VL by importing some of the nodes and concepts.
VL is made to create logic.
V4 is made to create content.
That’s how I’d put it. And this is also how the community for v4 is biased.
Now you could say that the specific problems that occur in very large projects are in fact language problems - not design problems - and may be overcome by the features of VL. But we might end up having a solution for the scaling issues, not being able to do design work anymore. That’s at least for the near future, and @joreg, sorry to say, but this is what I’m mostly interested in. I can’t wait another two years. We need solutions for these particular issues now.
I don’t see how these two ends could fit together. So I’m very happy to follow @joreg s invitation and analyze the problems and learn how he’d address them. I’ll report with our findings.