297 karma · joined May 30, 2015
NodeRED is a standalone tool than a "language", and although it's possible, using it to integrate with (and from) existing code is not trivial.
Flyde on the other hand, takes more of a "library" stance. It is agnostic to the code running it and can be easily embedded into other codebases.
With that being said, Flyde does offer an easy way for node authors to set local and global state, but in a functional way - you can pass your own map as the global state, and do whatever you want with it. It's not properly documented yet, but here's the code - https://github.com/flydelabs/flyde/blob/main/core/src/execut...
NoFlo.js was the closest to allowing this, but I think that it was too early for the game, and NoFlo took a non-integrative approach. Vladimir Sibirov wrote vastly about that and why he thinks it failed in this great blog post - https://blog.kodigy.com/post/state-of-flow-based-programming... I was happy to see Flyde addressed this
Other purely FBP implementations did not put enough emphasis on the visual aspect, which for me was crucial to nail on a holistic level.
And for your last question - my goal is for it to be used in production systems, yes. I plan to release a Flyde-based visual API builder soon - https://www.trigg.dev as a more specific use-case, and hope that the fact you can download the Flyde flows and run them wherever you want will help potential users overcome the fear of using a low-code tool.
Forgot to remove that after a docs rehaul. Tutorials still need to be re-written after some major changes, but perhaps this old blog post can give a sense - https://medium.com/@gabrielgrinberg/visual-programming-in-vs...
``` import { loadFlow } from "@flyde/runtime";
const execute = await loadFlow("./celsius-to-fahrenheit.flyde");
const inputs = { celsius: 0 }; // "celcius" is a main input in the flow, therefore it must be provided when executing the flow const { result } = execute(inputs); // execute returns a "result" promise, along with a cleanup function that can be used to cancel the execution.
const { fahrenheit } = await result; // each output in the flow is a property on the result object
console.log(fahrenheit) ```
(taken from https://www.flyde.dev/docs/integrate-flows/)
But your comment strengthens my feeling that making this more intuitive and discoverable and is indeed something I should prioritize
Flyde on the other hand is aimed to be used in the application layer of modern web development.
The combination of the Elm reference and "coarsely structure codebases around CPU timelines and dataflow" statement reminded me of this great talk by Evan Czaplicki (Elm creator): https://www.youtube.com/watch?v=XpDsk374LDE
Have to admit that the difference between the "before" and "after" UI in the video doesn't feel big enough. Did you consider removing also the "Projects" list on the left? Or reducing it?
Removed it immediately after staticautomatic pointed that out.