“There are only two kinds of languages: the ones people complain about and the ones nobody uses.”
Bjarne Stroustrup offered this line in a reflection on feedback from users of C++. Stroustrup explained that complaints once became an informal signal about which C++ features troubled developers, although that signal also caused him to underestimate the language’s user base. Many people quietly worked around problems instead of reporting them. Its force comes from experience: the speaker was describing consequences already visible in real systems and institutions.
The joke recognizes that widespread use exposes a language to more tasks, preferences, and criticism. Complaints can be evidence of real friction, but their volume also reflects reach. Perfect approval is not a realistic measure for a living tool. The line asks readers to look past novelty and examine what the technology enables people to do. It directs attention to the work between an appealing idea and a dependable result: defining the problem clearly, exposing assumptions, and learning from evidence instead of relying on reputation or momentum. In practice, that means asking what changed, who gained new capability, and how the result would be checked by someone who did not share the builder’s expectations.
Popularity does not excuse defects. Some users stay silent because reporting is difficult or because they lack influence. Maintainers still need structured evidence, representative participation, and the willingness to simplify features that create recurring harm. That distinction is essential whenever a compact quotation travels farther than the detailed account that produced it. Strong technology reporting must preserve this nuance, because the same words can support very different choices when the original constraints disappear. A responsible reading also separates the speaker’s documented claim from broader promises that admirers may attach to it later. That protects both the historical record and the reader’s ability to disagree intelligently.
Platforms and developer tools can learn from both halves of the line. They should welcome criticism without treating every loud opinion as representative, while actively seeking the quiet failures that support tickets and public forums never capture. Used this way, the quote becomes a prompt for better practice rather than a decorative line about innovation. For readers, builders, and institutions, the practical question is not whether the quotation sounds true in isolation, but whether current decisions honor the conditions and responsibilities it identifies. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. Those habits turn a memorable insight into work that others can examine and improve.
Bjarne Stroustrup offered this line in a reflection on feedback from users of C++. Stroustrup explained that complaints once became an informal signal about which C++ features troubled developers, although that signal also caused him to underestimate the language’s user base. Many people quietly worked around problems instead of reporting them. Its force comes from experience: the speaker was describing consequences already visible in real systems and institutions.
The source record connects the wording to a reflection on feedback from users of C++, which is the context used for this post.
The joke recognizes that widespread use exposes a language to more tasks, preferences, and criticism. Complaints can be evidence of real friction, but their volume also reflects reach. Perfect approval is not a realistic measure for a living tool. The line asks readers to look past novelty and examine what the technology enables people to do. It directs attention to the work between an appealing idea and a dependable result: defining the problem clearly, exposing assumptions, and learning from evidence instead of relying on reputation or momentum. In practice, that means asking what changed, who gained new capability, and how the result would be checked by someone who did not share the builder’s expectations.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
Popularity does not excuse defects. Some users stay silent because reporting is difficult or because they lack influence. Maintainers still need structured evidence, representative participation, and the willingness to simplify features that create recurring harm. That distinction is essential whenever a compact quotation travels farther than the detailed account that produced it. Strong technology reporting must preserve this nuance, because the same words can support very different choices when the original constraints disappear. A responsible reading also separates the speaker’s documented claim from broader promises that admirers may attach to it later. That protects both the historical record and the reader’s ability to disagree intelligently.
Platforms and developer tools can learn from both halves of the line. They should welcome criticism without treating every loud opinion as representative, while actively seeking the quiet failures that support tickets and public forums never capture. Used this way, the quote becomes a prompt for better practice rather than a decorative line about innovation. For readers, builders, and institutions, the practical question is not whether the quotation sounds true in isolation, but whether current decisions honor the conditions and responsibilities it identifies. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. Those habits turn a memorable insight into work that others can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.
