I think it's really interesting how now there seem to be a glut of options in the node-code genre coming about.
One of the things that really, really, rankles me, is NoFlo. I think that the people supporting this are whack and just don't know what's already out there.
Number ONE: There is a system that pretty much does every damn thing NoFlo is aiming to do, PLUS ALREADY HAS A NODE EDITOR.
Run a version here, in the browser!: http://idflood.github.io/ThreeNodes.js/
The master branch is here: https://github.com/idflood/ThreeNodes.js
Basically, you just download node.js (npm will probably be included I think), and then coffeescript. Make sure both are installed. Then get ThreeNodes.js, and you can run your own system.
THIS IS OPENSOURCE. THIS EXISTS ALREADY. THIS USES PRETTY MUCH ALL THE TECH THAT NOFLO IS MAKING YOU PAY MONEY INO A KICKSTARTER FOR.
Let's check some quotes from NoFlo's kickstarter page.
"If we hit our stretch goals, we will support native Android and iOS app development and Python!"
This belies a focus on mobile. Now, believe me, I realize mobile is a big market. BUT I NEED TO DO STUFF ON DESKTOP TOO. In NoFlo, DESKTOP=BROWSER.
$250K - Java Implementation (Android Apps)
$500K - Objective-C Implementation (iOS Apps)
$1M - Python Implementation"
Look at that. The top goal is a PYTHON IMPLEMENTATION. The bottom goal is a android/java implementation. I'm curious how relevant that is to most people that currently use node/patch type systems to code.
"The NoFlo UI is optional! The purpose of this Kickstarter is to fund the hosted UI, but NoFlo is usable right now as a code-only framework. Graphs can be created via JSON, procedurally or a fancy DSL. Components are shared with Github. For more info see the documentation."
So, there is 96,000+ dollars pledged to NoFlo, and THEY DON'T EVEN HAVE A UI!!!
Meanwhile, ThreeNodes.js is hanging out there for free, opensource. WHAT THE???? Node coders appear to be victims of hype.
"Facebook gets it - you can’t design gesture-rich UIs with a static tool like Photoshop. Instead, they went with Apple’s Flow-based tool, Quartz Composer (QC). Unfortunately, QC is only suitable for prototypes so everything has to be redone in code anyway! "
Here is where they betray that they are fucking idiots that do not know how to code, or use QC properly within an XCode project, as one part of an application. NoFlo guys, this is a stupid, stupid comment.
Good luck revolutionizing node coding with a system that works on the backbone you've chosen to build it on. Yikes!