NoFlo Kickstarter: The Hacker's Perspective
NoFlo Kickstarter: The Hacker's Perspective
Join the DZone community and get the full member experience.Join For Free
Atomist automates your software deliver experience. It's how modern teams deliver modern software.
This is our effort to bring visual and collaborative flow-based tools into the world of mainstream software development. Similar tools are already in use in many specialized industries from movie special effects to hardware simulation, but we programmers still have to construct these complex maps of our software's control flow inside our brains based on their textual representation. With your support, we could change that!
We've already reached a third of our goal on the first day. Clearly people see the need for these tools. Exciting times!
The stories from TechCrunch and GigaOm tell the story well for non-programmers. But based on the questions I've received today, I thought it would be good to clarify various points from a more programmer-centric point of view.
Hasn't visual programming been tried before?
The story of visual programming tools started with the GRaIL system of the 60s, and has progressed to tools like LabView and Pure Data. So far none of these tools has reached mainstream acceptance outside of their (sometimes fanatic) industry niches.
This is partly because these tools were built originally with a particular problem domain in mind, and partly because of the user experience. Execution matters, as we've seen so many times in the tech industry. After all, there were tablets a lot before the iPads.
With our team I have the confidence that we have the necessary skills and vision to build something that is actually a pleasure to use, and that makes it truly easier to work with the control flow of your software than it is with the text editors.
This is not a rehash of UML. UML is a diagram mapping out object-oriented constructs, often used for code generation. NoFlo graphs instead are only the coordination layer that manages the control flow of your software. The components are still handcrafted and unit-tested code that NoFlo merely wires together at runtime, following the edges specified in a JSON file. No code generation here.
Why map out the control flow?
All software is inherently a graph. Functions call other functions, sending data along. Signals are emitted and connections are made. But outside of some debugging tools we rarely see this in a visual format. Instead, when starting to work on a program you have to parse the code and build this map in your head.
This imposes a lot of cognitive load that tools like NoFlo could avoid. When you can see visually how things are connected, you can focus on the bigger picture and build the software you need in a more efficient way. This is what Bret Victor talked about recently.
What is the role for code, then?
My original NoFlo UI prototype already included the code editor for modifying and creating new components. By the principles of TDD, each component is always edited alongside its unit tests, and the tests can be run at any point with a single click. We're now bringing that back into the new UI:
For those who don't want this UI, NoFlo is still fully usable also without it. As a matter of fact, we don't have a UI before the Kickstarter succeeds, and yet many companies are already building their applications with NoFlo. One way is by using the
Another reason why the NoFlo development environment may succeed where many others failed is that programming has changed.
We no longer target a single protocol — whether the Win32 API or HTTP — in our applications. Instead, we need to talk multiple protocols and with multiple devices at the same time. Even just dealing with both REST and WebSockets is difficult to many traditional programming environments.
The other big change is the usage of different web APIs as part of your applications. Authentication, handling asynchronous requests and services that are sometimes down can be a pain.
NoFlo brings a controlling layer to your software that allows you to map out these scenarios and isolate the handling of each protocol or API into its own set of small, simple components.
Where could this be used?
Many of the nodal editing tools built in the past have been very domain-specific. However, flow-based programming is a general software development paradigm. NoFlo has already been used for a wide variety of tasks, including:
- Business data extraction and reporting
- Automating billing workflows
- Receiving, routing, and sending text messages
- Static site generation
- Building server-side web applications
Now that we added browser support it will be possible to also build physics-based user interfaces with NoFlo. There should be some interesting examples of that coming up soon.
How about open source?
If you're following this blog, you probably know that I feel strongly for software freedom. Everything I've done during my professional career has been possible only thanks to the open source community.
NoFlo and the UI we're building are and will remain open source available under the MIT license. As a matter of fact, the UI is designed to not only work with NoFlo, but also to be adaptable to work with other flow-based systems. I feel this is an area with a lot of potential for collaboration with the various functional and dataflow projects out there.
We will however be offering a hosted version of the software for a fee. The various Kickstarter rewards will give our backers an early and cheaper access to that.
But still, you'll always be able to run the whole stack on your own infrastructure if you choose to do so.
What happens next?
There are still quite a lot of days left in the campaign. Tonight I'll be flying back to Europe, and then we'll focus on the next steps.
One important area of attention is publishing more demos and examples of NoFlo in real-world use. I hope by early next week we'll be able to show a few applications running on both browser and Node.js. I will also publish our flow-based port of the Jekyll static site generator. These should help people getting started with this style of programming.
We also have quite a lot of content lined up and waiting for editing. Something of interest to everybody working with flow-based or functional programming will be the long cut of the interview we made with J. Paul Morrison, the father of FBP. My hope is that video will be live by the end of the next week.
Thanks everybody for helping to make this possible! Keep spreading the world and giving your support!
Published at DZone with permission of Henri Bergius , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.