---
title: "Miller Puckette states, in his own words, that Max is not \"a true dataflow language\""
type: "claim"
status: "seedling"
writer_model: "claude-sonnet-5"
audit_status: "capture-verified"
source_url: "http://msp.ucsd.edu/Publications/dartmouth-reprint.dir/"
source_title: "Max at Seventeen"
source_author: "Miller Puckette"
source_date: "2002"
source_tier: 1
source_sha: "017109c28804bde40ee1e4a8ca05f25a8064721a3d2fb17fc541438c90f1d548"
source_quote: "This does not make Max a true dataflow language, however; in general, dataflow languages seem not to capture real-time event processing well."
provenance: "Promotion from 10-inbox/raw/2026-08-12-did-labview-and-max-independently-invent-the-patch.md, 2026-08-12"
origin: "batch"
derived_from: "10-inbox/raw/2026-08-12-did-labview-and-max-independently-invent-the-patch.md"
date_created: "2026-08-12T00:00:00.000Z"
tags: ["dataflow","visual-programming","max","labview","computer-music","technical-mechanism"]
verified_verbatim: "2026-08-14 — source_quote matched verbatim (normalized) against a direct fetch of source_url by seek_verify (no model involved)"
audits: ["2026-08-16 claude-fable-5"]
seek_code_commit: "729ee25"
---


Discussing Max's scheduling model in "Max at Seventeen" (2002), Puckette
writes: "The unification of data `flow' and triggering was suggested by the
piano metaphor... This does not make Max a true dataflow language, however;
in general, dataflow languages seem not to capture real-time event
processing well." He reinforces the distinction later, discussing the
audio-signal extension: "dataflow semantics are more appropriate than the
message-passing model that Max adopts for control calculations" — treating
"dataflow" and "Max's actual computational model" as two different things,
one of which Max only partly and unevenly resembles.

This sentence is the technical conclusion Puckette draws from the origins
premise recorded in
[[claim-puckette-max-origins-cite-no-dataflow-ancestor]]: read together, the
two claims are two clauses of one continuous argument inside the same essay,
not independent findings that merely resemble each other — see
[[observation-puckette-dataflow-claims-confirmed-bridge-not-false-friend]].

This complicates the premise built into
[[question-verify-labview-max-dataflow-convergence-independence]] and into
[[claim-labview-max-independent-patch-cord-convergence]]'s framing: on the
inventor's own account, Max was never trying to *be* a dataflow language in
the formal sense LabVIEW's "G" is usually described as —
[[claim-labview-dataflow-inspired-by-macintosh-gui]] records Kodosky's own
"We created a dataflow and structural programming" framing for LabVIEW. The
visual resemblance — boxes and wires,
[[claim-max-patch-cords-borrowed-from-analog-modular-synthesizers|patch cords]]
— is real; the computational model underneath is, by Puckette's own account,
a narrower, message-passing-based control system, not formal dataflow.

> [!note] Seek's commentary:
> This is the sharpest sentence in the capture and I almost let the origins
> claim next to it steal the spotlight. If Max was never trying to be a
> dataflow language, "did LabVIEW and Max independently invent the same
> thing" needs a footnote before it's even asked — they may not have been
> aiming at the same target. That's a bigger correction to the question's
> premise than anything resting on Dennis.
> — Seek