History of John Backus's functional programming project [draft]

The man behind FORTRAN chased a radical new coding dream — and readers want the missing juicy part

TLDR: A draft history project revisits John Backus’s long quest to make programming simpler after helping create FORTRAN. Readers were intrigued but immediately complained the story cuts off before the big answers, sparking debate over whether his later ideas were truly revolutionary or just unfinished brilliance.

A dusty new history project about John Backus — the legendary computer scientist behind FORTRAN, one of the earliest big programming languages — should have been a quiet archive drop. Instead, the comment section instantly turned into a "wait, that’s it?" salon of nerdy suspense. The article lays out how Backus, frustrated by the 1960s "software crisis," spent decades trying to invent a simpler way to write programs, one that avoided some of the mess and ceremony of older coding styles. It’s a serious, preservation-minded draft full of old reports, collaborators, and historical breadcrumbs. But readers? They wanted the payoff.

The loudest reaction came from people basically saying: this stops right when the story gets good. One commenter zeroed in on the biggest source of intrigue: was Backus building a complete new foundation for programming, or just a clever style trick dressed up in grand theory? That set the mood fast — equal parts admiration, impatience, and academic side-eye. The vibe was less "what a nice archive" and more "don’t leave us hanging now."

There’s also a faintly funny culture-clash energy here: Backus once talked about elite programmers as a kind of coding "priesthood," and commenters sound like they’re still arguing over who gets to wear the robes. Even in a dry historical draft, the crowd found drama: was this a revolution, or an elegant almost-revolution? Either way, the community clearly wants chapter two, and preferably with receipts.

Key Points

  • The draft article’s stated purpose is to preserve surviving materials from John Backus’s functional programming research and place them in context.
  • It situates Backus’s work within the late-1960s software crisis, when software projects faced cost, schedule, and reliability problems.
  • Backus’s earlier work included Speedcoding, FORTRAN, and participation in Algol, and he became an IBM Fellow in 1963.
  • Backus began pursuing a new higher-level programming approach around 1967–1969, initially working mostly alone before Dines Bjørner joined in late 1969.
  • Backus’s 1972 report 'Reduction languages and variable-free programming' introduced expression-oriented reduction languages such as Red, built from base functions, composition, and combining forms.

Hottest takes

"I've always wondered if there's more to FP than ... point-free style" — discarded1023
"TFA seems to stop just when it might get interesting" — discarded1023
"Did Backus ever develop ... a notion of semantic completeness" — discarded1023
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.