Thank you for the answer @joreg .
Reading this answer, and after seeing the node 17 keynode, I have questions about the future of VVVV.
Or maybe just one question: does VVVV has a future?
In the keynode, we can understand (between the lines) that VVVV will never have an app exporter, a crossplatform version, a timeline (by the devvvvs)… But VL will.
For me, VVVV and VL are totally different beasts, and are made for different users.
I remember when I started VVVV, it took me a few hours to understand the basic concepts, and to be able to create a small project (I was a designer, not a developer at all)
For VL, I assisted all the VL workshops at Node17 (the basics by joreg, the concepts by tonfilm and elias, and the VL project by sebastian and anton). I watched hours of workshops from youtube (the most interesting was this one: https://www.youtube.com/watch?v=hUuMMA1JEko&index=1&list=PLG540xv6kfGFIXYVV_hmOZ4U0lGgDuA11). But I’m far away from being able to use VL for any small project.
I know it’s the beginning, everything will be easier when the documentation will be here, the help-patchs..
But for sure, the learning curve of VL is, and will be, harder than VVVV.
I’m happy to see advanced users like dottore or velcrome doing magic things using VL, importing some new libraries easily…
I will try again later, maybe in one or two years, when VL will be more robust.
But I don’t want to replace totally VVVV by VL, it’s too different, I do not find what I need and like with VVVV in VL.
For me, VVVV is a language more than a software, and I like the “granularity” of this language (the ratio between the number of nodes used and the complexity of the result)
It’s just perfect for me. I would not change it for Max, PD, TouchDesigner, or any nodal system possible.
VVVV allows me to prototype something in a few minutes, in every field possible (sound, 3D, video, databases...). I can teach VVVV in a few hours to people who have no idea of what programming is (People like me, who don’t know and don’t want to know what are generics, state/stateless patchs, recursion… People who just want to be able to code things visually, without writing code…)
On the other hand, I can create very complex systems with the simplicity of VVVV: I worked on the Immersio performance, http://immersio.tv/, the virtual reality experience with the clarinet we played at Node17 Off :)
It’s not as complex as the @eno impressive project tree before in this post, but the result is very complex, when the patches behind it are simple. Like Eno said before, the most complex task was to manage the scale of the project (a LOT of workarounds to de-evaluate things, to optimise, to load and unload things at the right moment…). For me it’s a major weakness of VVVV.
Could you make a clear statement in a blogpost about what is the future of VVVV ?
Because it’s never clearly said, but all the indicators since last year go in the direction of: “no more new features for VVVV, everything new is for VL”.
What I (we?) would like to hear, it’s something like: “ok, we worked hard these last months on the Import Library thing for VL, it will be a game changer for both VL and VVVV, but now we are coming back into VVVV on the next months to give you some long awaited things…”
(the UI in a separate thread, the crossplatform app, the app-exporter, the integrated timeline …?) .
But I'm afraid you will rather say something like: “forget about VVVV, it’s something from the past, look at the future, VL is the perfect tool for you…”