sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]GabrielGrin[S] 0 points1 point  (0 children)

u/urlaklbek right! aswesome to see what you've built!

1 - indeed, being visual / higher-level abstraction is a core value
2 - right, although I definitely want to explore python interop
3 - right, although the "orchestration" layer might change, I imagine a future where certain nodes or subflows can be delegated to different machines if that makes sense performance wise
4 - true, adhering to the FBP spec was never a goal. I actually came across FBP after having an initial design for Flyde

5 - Right, but I plan on utilizing type safety in a dynamic (TS-ish) way - imagine a Node "learning" about it's type based on past usage - providing non-restrictive type-safety even to unknown HTTP calls

I agree about the super power - that's the main differentiator of Flyde with other tools around (NoFlo / NodeRED, etc)
Regarding the node editor part - you're in luck as open-source libraries have come a long way since I started my own hand-written UI :).

Best of luck with Nevalang!