It's been a while again since we last dropped news about that next big thing we still call vvvv50 (50). So in order to get the hype slowly started here are some further notes...
First a quick recap of what we have with vvvv45 (45) so far: For the first ~6 years in existence vvvv was a rather monolithic thing. We sloppily called it "a multipurpose toolkit" and really only later found out ourselves that it was actually made of 4 parts:
Still very much monoltithic in that there was no way for the user to change any of those. Only when in 2008 we introduced the plugininterface vvvv became more modular in that it allowed users to create their own nodes, and boy they did (->addonpack, dx11-pack, cv.image-pack, ...).
So the library part was addressed but critizism remained:
According to the great Joel Spolsky the single worst mistake you can do when writing a software, is starting from scratch. So we did.
So here is our bold plan, this is what we're aiming at (longterm):
Now if that sounds familiar as in "so whats the big difference?" then exactly. Instead of saying it will be completely different we can also say that it will be very much the same only much better. People tend to prefer hearing either. We couldn't decide...
Anyway we're at a point with this where we have bits from all 4 parts implemented and can do simple demos. But mostly we're still focusing on the "visual programming language" which we consider the foundation of the pleasure we want you to have with 50.
The great thing about 45 is still that it is simple to learn. Say that again..!? No really, if you approach it the right way (arrogant!) it actually is. There is a huge library of nodes that is hard to grasp, true, but the things you have to know about the visual language vvvv are only a few:
Those are basically the language features of 45. Specifically the concept of Spreads is what makes vvvv stand out. It allows you to do simple things quickly but as things get more complex they are quite cumbersome to work with. We call this "low-level" while the goal of our new visual language is to be able to work more "high-level", ie. less thinking about concepts that make things easy to understand for the computer but more thinking in human terms.
So with 50 we're introducing a number of new language features that will make it easier for the user to create more complex programs. Here is the buzz of what we have so far:
Sounds scary? Naa... you'll see, all a breeze. Really the basics are not changing: You'll have nodes and pins to connect, a renderer, a quad, ... nothing new. If you're not using any of the new features you can still work kind of 45-style only then you'll not be seeing any of the productivity-increase you can gain from using them.
Specifically as you'll not need to use them all right away and you'll be using them without noticing anyway. But in order to talk about them we need to call them names.
In a forthcoming series of blogposts we'll show you how working with those features will feel like. If you already like what you've read so far and want to buy the cat in the sack we're always up for a /downloads|vvvv?.
anonymous user login
~8h ago
~2d ago
~6d ago
~6d ago
~7d ago
~8d ago
~19d ago
~28d ago
~1mth ago
~1mth ago
...you're always up for a... ?
Ahhhh all this suspense is killing me =)
my benchmark in terms of ease of use would be the amount of nodes and clicks to achieve the same results. there are some good examples in history were this went wrong, well code-wise like bloated actionscript 3
let's finish beta stage first?
gimme moar!
excited!
++
sounds great. no point asking for a release date i know that
Sounds awesome guys! Can't wait!
nice one! seems that a rewrote is the only thing that will really work after reading this lovely article :) but maybe he was never used to work with lot of visual binsizes.
Thank you for your continued development!
I have a couple of quick questions:
Best ..
@gareth it seems you're not seeing the flattr button..
@curveau: re opengl: this is a library-question and we're not taking library yet. but if you read in between the lines you read: dx, gl, mantle, anything anyone will implent. re web/js see http://vvvvjs.com
OK, cheers dude
Another quick question:
Can somebody answer my lame question, please: what language VVVV actually supports? It is possibe GLSL shaders in this software? Thanks.
@quadrelli: as propaganda states, the currently available version of vvvv supports the vvvv visual language, c# and hlsl.
this blogpost talks about a different software that _may at some point in time support GLSL. but thats far off the topic of this post.
Will this run in Linux? Please
uhhh sound great :D