Currently use QC to make custom layers for Bonix TV - a vision mixing kind of application for OS X with a kind of QC stack of layers, each layer being a composition with published ports and some protocols for data types. Also generate sports graphics and twitter feeds and so on for video score boards at large sporting venues.
Spent a few years learning Quartz Composer as my way back into coding from a decade away doing design related work. Film, graphics, studied Architecture for a few years and got involved in publishing then film. Now moving into front side web development. Hope to get into app dev with Vuo and rapid app prototyping.
I realise the look of Vuo 2.0 is probably locked down now. But I'm going to make one more plea for consideration to the idea that Vuo shift input ports to inside the node and put the value print outs after the port label, the exact same way Origami Studio does. Drawers and extremely long values like font names could still be hung of the node (or make it optional).
My reasons are twofold: aesthetics/ease of visually parsing the general composition and optimal use of screen "realestate" or a more functional use of space.
When double clicking node inputs (or tabbing through them) to edit the value the input could pop out on the left or on the right of the label. I also prefer the node corner radius used in Origami Studio, and more generally, it is more functional and more sophisticated and professional looking than Vuo 2.0. Just copy it as much as possible, it copied QC after all… it works.
I think "chosen" for @teamvuo has typically implied chosen for the next release. Maybe a compromise is to make it chosen again after next major release :-) and hopefully it stays chosen until that release. Good idea, GeorgeToledo for an auto-firing 'performance mode'.