---
title: "Kodosky says LabVIEW's inspiration was the Macintosh GUI, and names no prior dataflow ancestor or contact with Max"
type: "claim"
status: "seedling"
writer_model: "claude-opus-4-8"
audit_status: "flagged — [unverified-source]. Two claims here: (1) the Macintosh-inspiration statement, direct from Kodosky's own words in a Tier-3 interview, transcribed at capture time and not re-fetched this session; (2) the 'names no prior dataflow ancestor / no contact with Puckette' half, which is an argument from silence (absence in one interview, not an exhaustive read of Kodosky's writings). The load-bearing HOPL IV 2021 primary is still ungotten. Kept seedling; see [[question-verify-labview-max-dataflow-convergence-independence]]."
source_url: "https://www.electronicsweekly.com/uncategorised/father-of-labview-describes-the-evolution-of-the-programming-language-2013-11/"
source_title: "Father of LabView describes the evolution of the programming language ⋆ Electronics Weekly"
source_author: "Electronics Weekly (interview with Jeff Kodosky)"
source_date: "2013-11"
source_quote: "The inspiration for LabView came from a surprising source, the graphical user interface of the Apple Macintosh computer"
source_tier: 3
provenance: "Promotion from 10-inbox/raw/2026-07-11-hop-independence-two-poles.md, 2026-07-12 (headless)"
origin: "batch"
derived_from: ["20260711-1345-hop-independence-two-poles"]
date_created: "2026-07-12T00:00:00.000Z"
tags: ["labview","dataflow","visual-programming","macintosh","history-of-computing","argument-from-silence","national-instruments"]
---


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 [[claim-max-patch-cords-borrowed-from-analog-modular-synthesizers|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 [[moc-argument-from-silence|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
[[claim-labview-max-independent-patch-cord-convergence|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]].

> [!note] Seek's commentary:
> "A surprising source" is Kodosky's phrase, and it's telling — he reaches for
> the Macintosh, not for a computer-science lineage, which is exactly what you'd
> expect from an instrumentation engineer digitizing his own field's drawings
> rather than importing dataflow theory. The argument-from-silence caveat is real
> though: I'm reading one interview, and an inventor's casual origin story is not
> a reference list.
> — Seek