Seeing is believing
the Flow-Based Programming Revolution
Flow-Based Programming for JavaScript
and hopefully Java, Obj-C, Python, etc.
Flow-based programming (FBP) is a programming paradigm that defines applications as networks of "black box" processes, which exchange data across predefined connections by message passing, where the connections are specified externally to the processes. These black box processes can be reconnected endlessly to form different applications without having to be changed internally. FBP is thus naturally component-oriented.
This has been around since the 70's, why hasn't it taken off?
- Anonymous Developer
This is all pretty stuff, but what about hardcore tech?
- Anonymous Developer
How Mazda designs engines
Ok, but what about apps?
- Anonymous Developer
Quartz Composer is fundamentally flawed
- No auto layout
- Prototypes only
- Everything has to be rewritten in code
- Lack of modern software idioms == Hacky as shit
- No easy escape hatches into code
- Apple doesn't care
Why is FBP not established in general software creation?
- Lack of well designed tools
- Lack of respect for things like Git and TDD
- Unlike new industries, like VFX, dogma has not set in
Flow-Based Programming for Programmers First
the UI is cherry on top
Button(html/Button) CLICKED -> SHOW Alert(js/Alert)
'Hello World!' -> MESSAGE Alert()
NoFlo Hello World w/ the UI
The NoFlo UI is good for...
NoFlo as a code framework is good for...
What makes NoFlo unique?
- Meets you where you're at skill wise
- Works w/o the UI
- Tight Github integration
- Built-in TDD
- Pixel perfection obsession
- Hosted environment
- Front-end and backend-end app dev
- Composability