There is a discussion going on about the store, in which @StiX brings up the difference between the Unity user base and eco-system and vvvvs.
I’m not a Unity user so I shouldn’t making claims that some things are easier in one piece of software that the other, but I feel that the multi-purpose use of vvvv is still its strong suit. I do some 3D but the aesthetic I go for wouldn’t suit the Unity, to my knowledge.
As much as I wish someone would modernise vvvv’s core media features, I think the dev should continue concentrating on the language. I’ve always thought of vvvv as an easy to learn alternative to Processing, Openframeworks, Cinder, but perhaps a better comparison might be Touch Designer. I’m not going there, though.
But if @vux had never come along and added tons of the features we use so heavily (not just DX11 but many of the addons we overlook, @woei et al) maybe they would have been filled in by someone else but who knows? In Openframeworks there are obviously lot of c++ devs out there happy to contribute to new libraries.
vvvv’s issues are different. They’ve created V++ and they now need c/c++ programmers and assembly coders to come up with libraries for it.
The problems are that
a) it ain’t easy to extend and
b) the size of its userbase.
So what’s the solution? In theory its VL: extendability, deployability and lots of documentation, but I digress.
I think the eco system the vvvv devs want to foster is more akin to OpenFrameworks, but the expertise among the users hasn’t been large enough to create that sort of open source community where cutting edge libraries are being ported and shared as soon someone can think of a good use for them. Vvvv is nearly there, but it relies on the time of too few really good and generous coders who want to see vvvv succeed as a program and as a community.
So why is that? Why aren’t there more users? And how can we increase the number of users across the art, design and software engineering spheres?