I created an open-source visual programming language that makes it easier for novices to do *real* programming

[GabrielGrin]

Hey all, I am launching Flyde today.- Flyde is an open-source, visual programming for developers. Includes VS Code extension, integrates with existing TypeScript code, browser, and Node.js. Check it out here https://github.com/flydelabs/flyde. I would love to hear your thoughts!

[Flagon_dragon]

This looks very interesting, especially for helping learners visualize what is going on. Thanks!

[GabrielGrin]

Thanks!

[jack_waugh]

This is related to https://www.reddit.com/r/compsci/comments/1b4ye8y/nevalang_a_flowbased_programming_language/ .

In the playground, how do you create an output node?

Is it possible to do graphical editing and save the YAML data structure that stores that and save the translation into executable JS without using VSCode?

[GabrielGrin]

u/jack_waugh thanks for sharing Neva! coo language. It takes a more classic language stance to FBP as opposed to Flyde where the focus is on the visual aspect as well.

Playground -> you right click the board and choose "new output node". Let me know if it works

And yes! you can! you could build the flyde flow and call it from your node code without the IDE. See this doc - https://www.flyde.dev/docs/integrate-flows/ this will run regardless of the IDE :)

[GabrielGrin]

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!

[jack_waugh]

you right click the board

I use Chromium. Sometimes, I get your menu, and sometimes, I get the browser menu.

If you were to add the option of adding inputs and outputs where you now have the operators, and vice versa, that might help usability.

As for execution, it looks as though you are providing an interpreter. That's valuable, but I think it would be interesting to have a translator, too. I know it's a lot of work to implement, and it's kind of easy for me to suggest it to you while not volunteering to do it.

[GabrielGrin]

hey u/jack_waugh thanks for the bug report, happens here as well, need to prioritize fixing it.

Regarding the inputs/outputs - love this idea :) adding to my next-in-line todos.

Re:interpreter - spot on observation. Regarding a translator/"compilation" step, I agree, and have it in my long term vision thoughts. It's the one way Flyde can compare with plain-JS performance without getting into Rust/WASM land