Show HN: Flyde – an open-source visual programming language

Original Article ↗ Hacker News Discussion ↗

Overall reception

  • Many find Flyde impressive, polished, and well-positioned as a complement to textual programming rather than a replacement.
  • Strong appreciation for its focus on interoperability with existing JS/TS codebases and the ability to run flows as a library.
  • Skeptics question whether a new visual language can succeed broadly and whether node graphs scale for complex systems.

Visual programming: strengths and limits

  • Advocates argue visual programming is still underexplored, especially for:
    • Delegating domain-specific concerns via well-defined nodes.
    • Making async/parallel behavior and dataflow spatial and intuitive.
    • Letting non-programmers or juniors build logic without deep syntax knowledge.
  • Others note VPLs have existed for decades (LabVIEW, Simulink, PLC languages, Pure Data, Scratch, etc.) and work best in domain-specific or highly interactive contexts.
  • Key weaknesses cited:
    • Poor ergonomics for large workflows; graphs become unreadable “spaghetti.”
    • Harder diffs, version control, search, and rapid input compared to text.
    • Planarity/2D layout limits and difficulty representing branches, loops, and rich algorithms compactly.

Flyde’s design choices and comparisons

  • Positioned as a JS/TS-first flow-based system that embeds into existing apps (VSCode integration, Node/browser runtime), in contrast to standalone tools like Node-RED or n8n.
  • Execution model: async, message-based, functional-reactive leaning; nodes have error outputs and can model parallelism and Promise-like behaviors.
  • Some prefer Blueprint-style “function with parameters” nodes and richer visual cues for execution vs data flow; current pin model is seen as flexible but sometimes cluttered.
  • Compared frequently to Node-RED:
    • Node-RED praised for ecosystem and UI-building, but criticized for single-input message model and excessive data-shuffling.
    • Flyde is viewed as lower-level, more integrative, not (yet) a Node-RED replacement.
  • Future/desired features mentioned: better auto-layout, zoomable hierarchical graphs, live value visualizations, JSON file format, web-component editor, multi-language support.

Use cases and pedagogy

  • Suggested applications: web backends, visual API builders, Discord bots, Reverse ETL workflows, mechanical/engineering calculations, education for kids and non-devs.
  • Several see it as great for learning concepts like concurrency; others stress that for complex business logic, plain text will likely remain primary, with tools like Flyde as higher-level orchestration.