2 ms·
Do you think such tools are mature enough for wide adoption yet? How does, for instance, version control and collaborative development fit into these flow-based
by JosephRedfern 9y ago
Do you think such tools are mature enough for wide adoption yet? How does, for instance, version control and collaborative development fit into these flow-based tools?
> every time you forsake a standard modular component in favor of your own way of doing it, you're creating technical debt for whoever has parse your code later
I don't disagree that you shouldn't re-invent the wheel whenever possible, but modularity is absolutely not unique to flow-based programming. Well designed libraries should provide good levels of abstraction and be highly modular. Flow-based programming might stop people from shooting themselves in the foot, but I'm not sure if the cost to flexibility makes it worth it in every case.
- deleted 9y ago[deleted]
- anigbrowl 9y agoYes, look into Flowstone or NoFlow. Tools like this are very common in many niche domains; it takes some mental effort to pull back and see the limitations of path dependency in general purpose programming, and frankly an awful lot of people are ego-invested in their current way of doing things with no thought to the long term accessibility and maintainability issues.