Wow :)

Working on a 1.0.0 launch for Flyde - https://flyde.dev/, an open-source visual programming language. It works great for embedding visual AI flows for backend logic. Integrates with TypeScript code, runs on VSCode & Node.js (via a runtime library, in-repo, no containers needed)

Would love to chat with people looking to combine n8n-ish capabilities in their code!

You theoretically could. Not sure it's the right tool for the right job.

We believe that many programming tasks are better done with textual coding.

Interpreting Flyde (the visual programming language behind Flowcode) flows and running them (see https://github.com/flydelabs/flyde/blob/main/core/src/execut...) ) will not benefit from being visual. It's mostly synchronous, borderline fractal logic.

A great use case for visual programming would be a task that involves several LLM calls, third-party vendors, and some transformation logic on top.

Looks like it! Best of luck with midio.com, looks like a great product.

OP here. At least a dozen times :) He was the inspiration of starting to work on https://github.com/flydelabs/flyde, the visual-programming language powering Flowcode.

Nope - we're both visual nodes-and-wires based tools, but they create a visual representation of your codebase/architecture, while we allow you to create the applicative logic visually.

Thank you!

I checked your project, loved the idea and implementation! Played with it a bit, was very slick. Going to read the paper soon. Congrats

PS1: A poster about Flyde, the visual-programming was accepted to VL/HCC 23 - https://conf.researchr.org/details/vlhcc-2023/vlhcc-2023-pos... PS2: We call our AI copilot "Flowpilot" as well :D

Node-RED is a great tool, especially for IoT and pure automation use-cases.

It's far from ideal when it comes to integrating with existing codebases and building backend features.

We're not competing with it directly, as we're aiming to be integrated into applicative production workflows.

Re: docs, 100%, it needs tons of improvement.

Error handling is a first-class citizen in Flyde, the visual programming language powering Flowcode. Any node has an "output pin" called "error" that will emit data if something goes wrong.

You can test this real quick in the playground - throw in a JS expression and write some gibberish and test your flow. Alternatively, use the HTTP node with a non-existent URL

Hey, author here. Thanks!

When I started Flyde, the underlying visual programming language powering Flowcode, I went for DOM as it was the simplest solution to get something working. I was sure a rewrite to WebGL/Canvas would be needed to be performant, but we managed to render pretty complex flows and leverage the ever-growing React ecosystem. Also, react-flow was in its infancy when I started, but even later, as it evolved, I still prefer to have full control over the experience. I strongly believe that the editor and the ergonomics of the "language" are inseparable, and if you want to build something truly great, you have to control the experience end-to-end.

I do think one day WebGL/canvas might be required to take the editor to the next level. One example I always think of is this one - https://xai-primer.com/tool/ It's a great UX solution for nested flows (something Flowcode supports). But as long as I can stay with DOM, the better.

Re: deepwiki - thanks for that! very cool website and LLM usage