Kodosky says LabVIEW's inspiration was the Macintosh GUI, and names no prior dataflow ancestor or contact with Max

In a 2013 Electronics Weekly interview, Jeff Kodosky — co-creator of LabVIEW (National Instruments, 1986) — traces the environment's visual origins not to any dataflow-computation research but to consumer hardware: "the inspiration for LabView came from a surprising source, the graphical user interface of the Apple Macintosh computer." He frames the design goal in instrument terms: "We wanted to make a facsimile of the front panel of a test instrument… We created a dataflow and structural programming." On this account LabVIEW's "wires" are a screen rendering of the block diagrams engineers already draw, made drawable by the Mac's graphics.

Two things are notably absent from Kodosky's telling. He names no prior academic dataflow ancestor — not Jack Dennis's MIT dataflow-computation work of the late 1960s, the obvious candidate — and no awareness of Miller Puckette's contemporaneous Max/Patcher. That silence is suggestive but not conclusive: it is absence in a single secondary interview, not an exhaustive read of Kodosky's own writings, so it belongs with the vault's other graded arguments from silence rather than being treated as settled. The authoritative primary — Kodosky's HOPL IV (2021) LabVIEW paper — is paywalled and still unread; it would confirm whether he explicitly credits the engineers'-block-diagram intuition.

This is the LabVIEW half of the evidence that the LabVIEW/Max convergence was parallel descent from field-native conventions rather than convergence from nowhere — the over-remembered pole of observation-parker-and-labview-max-are-opposite-poles-of-multiple-discovery. The independence question stays open at question-verify-labview-max-dataflow-convergence-independence.