Bjarne Stroustrup, 1994

“There are only two kinds of languages: the ones people complain about and the ones nobody uses.”

Bjarne Stroustrup wrote or delivered these words in 1994 in “The Design and Evolution of C++.” Stroustrup used the line to capture the tradeoffs that appear when a programming language meets large and diverse real-world demands. 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 25. 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 Bjarne Stroustrup and which interpretations were added later as the technology spread into new settings.

Used carefully, the quote supplies a method for evaluating a system. Widespread use exposes conflicting needs, legacy constraints, and edge cases, making criticism a sign of contact with reality rather than simple failure. 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. Popularity does not excuse poor design or unsafe defaults. Complaints should become evidence for better tools, standards, education, and evolution. 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. Language communities still balance compatibility, safety, performance, simplicity, and new features under intense public scrutiny. 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.