|
|
|
|
|
|
by threecheese
409 days ago
|
|
|
Looks very interesting. I am currently researching node-based developer tools and libraries, and after a quick look at your code I wonder why you chose to create your UI from scratch instead of using a diagramm-ish utility (react-flow and many others)? I know there are some tradeoffs with each, like one might be geared toward drawing, another for graph visualization, another for lots of nodes etc, and so maybe you didn’t like these tradeoffs? btw, https://deepwiki.com/flydelabs/flyde |
|
|
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