Demos, documentation, and specification — your path to understanding Pipe

Pipe is a visual programming language designed to match the power of text-based languages like Python and Java. Full details of the project can be found here: https://www.pipelang.com .
Since publishing the complete formal specification earlier this year, I've received hundreds of questions from developers curious about the language. Here's a guide to the key resources available today.
The #1 question I get: When can I actually use Pipe?
The IDE is currently in development and not ready for public testing yet. Pipe has a sophisticated formal semantics, so building quality tools takes time. However, I created a 3-minute video walkthrough showing how Pipe handles a real-world business problem: calculating bank account interest across deposits, rate changes, and balance updates.
Watch the demo:
This example comes from Section 3.2.3.16.5 "Business Case" in the specification, where I break down the diagram step-by-step. More demo videos covering different use cases are coming soon.
The demo on video covers the following cases (a corresponding input name is provided in parentheses after a case name):
Deposit (DEPOSIT) – storing new interest rate, new balance, and today’s date as a starting time for future interest calculations. No interest calculation is performed.
Interest calculation (CALCULATE) – interest rate calculation with the current interest rate and current balance for the period since the last operation.
Interest rate change (RATE) – storing new interest rate and calculating interest with the previous interest rate and current balance for the period since the last operation.
Balance amount change (BALANCE) – storing new balance amount and calculating interest with the previous balance amount and current interest rate for the period since the last operation.
For a quick introduction to the language fundamentals, read "Five Pillars of Pipe" - a 10-minute overview of the five architectural concepts that make Pipe different from traditional visual languages:
Read it here: https://peerlist.io/toplinesoftsys/articles/five-pillars-of-pipe
This article covers:
Memlets (explicit memory blocks)
Sequential signal processing
Type domains and overlaps
Hybrid visual-textual programming
Deep ecosystem integration
If you're wondering why another visual programming language when LabVIEW, Scratch, and Node-RED already exist, read "Visual Language Pipe as Integration Layer of AI-Generated Components":
Read it here: https://peerlist.io/toplinesoftsys/articles/visual-programming-language
This article explains how Pipe addresses key problems of software development: a need to create comprehensive and unambigous software specifications for AI code generation. Pipe can play a role of “dynamic specifications” where changes in requirements do not necessarily result in submission of full amended specifications to AI. Instead, Pipe visual workflow can be modified directly to reflect specification changes.
While Pipe was designed to complement AI code generation tools, it works just as well as a standalone language.
The full language specification (155 pages covering syntax, semantics, type system, memory model, and execution rules) is available free in three formats:
This is a deliberate strategy to separate formal semantics from implementation.
Many visual programming languages lack formal specifications entirely, relying on "learn by example" documentation. Others have specifications tightly coupled to their IDE's UI.
In contrast, every serious text-based language (Python, Java, C++) has a formal specification abstracted from any particular implementation. This allows multiple compilers, interpreters, and tools to implement the same language consistently.
By publishing Pipe's specification first, I'm establishing it as a language, not just a tool. This positions Pipe to compete with text-based languages on equal footing.
0
1
0