|
I think well-structured and designed landing pages are too infrequent, so I like the OP on that alone...and being an optimist, I'm always a little excited when I hear of a new paradigm, or an iteration of it...because that means that there is a (slightly) new way of thinking about and doing things...maybe even better than my own. Either way, I like that the opportunity exists (even if I never get around to thoroughly investigate it). And I know a lot of this is promo-copy, but this kind of stuck out to me: > Focus on the right areas without fear of constant conflicts, code reviews and lengthy onboarding processes. Again, I'm not experienced in the flow-paradigm...but I just have to guess that the need for code reviews is not because traditional code is not visual enough. In fact, I'd argue quite the opposite... a visual diagram offers some great big-picture benefits, but at the loss of granularity...if anything, I'd think a flow-based paradigm would require as much code review as before, but perhaps with a different mindset. I also think the background image for "Drag, Drop, Connect, Build" is...not inspiring to me. I mean, it's useful in some respects for overview of dependencies, maybe...but dragging-dropping and interpretation of visual symbols is not always more efficient than pure textual concepts. In fact, I'd argue that it can be even less efficient. How easy is it to examine the underlying abstractions behind connecting one pipe from one icon to another? |
Depends on the runtime you're talking to. For example MicroFlo on an Arduino behaves quite differently from NoFlo on Node.js
In NoFlo each connection is basically connecting an event emitter to an event listener. So, what happens is a JavaScript addEventListener operation.