John Backus, 1978

“Conventional programming languages are growing ever more enormous, but not stronger.”

John Backus wrote or delivered these words in 1978 in “Can Programming Be Liberated from the von Neumann Style?.” Backus used his Turing Award lecture to criticize languages dominated by step-by-step state changes and to propose functional alternatives built from composable forms. The surrounding work gives the sentence its real force. The date assigned to this NewsStreets series is a calendar placement, not a claim that the quotation originated on March 20. Restoring the source keeps the words connected to the problem, audience, and technical conditions that made them meaningful. It also shows which part of the argument belongs to John Backus and which interpretations were added later as the technology spread into new settings.

Used carefully, the quote supplies a method for evaluating a system. Adding syntax and features does not necessarily improve the power to reason about programs or combine solutions cleanly. Teams can apply that insight by naming the outcome they want, identifying the people affected, and choosing evidence that would reveal whether the design actually helps. A memorable quotation is useful when it sharpens a decision: architecture, interface, governance, maintenance, or the allocation of power. It is less useful when it is used to borrow authority without examining the speaker's reasoning. In practice, the principle should change a review question, a test plan, or an ownership decision rather than merely decorate a presentation.

Its usefulness depends on resisting an overly simple interpretation. No single paradigm solves every problem. Functional ideas can improve composition while stateful, object-oriented, logic, and dataflow approaches remain useful in appropriate contexts. Technology operates inside organizations and communities, so performance on a narrow benchmark cannot settle every question. Responsible practice makes assumptions explicit, documents tradeoffs, invites criticism, and provides a way to correct harm. That discipline does not weaken innovation; it gives ambitious work a clearer relationship to evidence and a more honest account of who carries the risk. A careful reader should therefore ask what the quotation leaves outside its frame, which stakeholders are absent, and what contrary evidence would require a different conclusion.

Today the quotation can be tested against systems used at global scale. Pure functions, immutable data, map-reduce systems, and modern language features show the continuing influence of Backus's critique. For individuals, the quote can guide the next choice without pretending to supply a complete formula. For organizations, it can prompt clearer goals, better measurements, and more accountable ownership. Its lasting value lies in translating an influential idea into careful practice: understand the source, test the claim, keep the limitations visible, and revise the system when real users or real conditions contradict the preferred story. The standard is not admiration for a famous technologist; it is whether the idea helps people build systems that are more understandable, dependable, useful, and worthy of trust.