Brave Search

The "Worse is Better" paper is an influential software design philosophy originally articulated by Richard P. Gabriel in his 1989 article titled "The Rise of 'Worse is Better'". This work contrasts two design approaches: the "New Jersey" style (Worse is Better) and the "Boston" style (The Right Thing), arguing that the former prioritizes implementation simplicity over interface simplicity, correctness, consistency, and completeness.

Gabriel's philosophy posits that software designed with implementation simplicity as the highest priority will spread more rapidly, become widely adopted, and eventually evolve into a complete system, whereas systems designed to be perfect from the start often fail to gain traction. This approach is famously associated with the success of Unix and the C programming language, which Gabriel describes as "computer viruses" due to their rapid propagation.

While Gabriel later expressed regret for the paper's impact, suggesting it warped the minds of youth and was "corrosive," the concept remains a significant topic in software engineering discussions. Critics, such as Nickieben Bourbaki (a pseudonym for Gabriel's friend), have argued that the dichotomy is a false one, as no one actually follows a pure "worse is better" philosophy, and the trade-offs often depend on external constraints rather than a specific design dogma.

AI-generated answer. Please verify critical facts.

What are the key differences between 'Worse is Better' and 'The Right Thing' design philosophies? How did Unix and C programming language embody the 'Worse is Better' principle? What criticisms have been raised against the 'Worse is Better' philosophy?

Dreamsongs

dreamsongs.com › WorseIsBetter.html

Worse Is Better

But a month or so later, I wrote a second one, called "Back to the Future: Worse (Still) is Better!" which was in favor of it. I still can’t decide. Martine combined the two papers into the single position paper for the panel, and during the panel itself, run as a fishbowl, participants routinely shifted from the pro-worse-is-better side of the table to the anti-side.

Stanford CS

cs.stanford.edu › people › eroberts › courses › cs181 › projects › 2010-11 › WorseIsBetter › index43bb.html

Main Page - Worse Is Better

This article argued for a design philosophy he dubbed worse-is-better in which implementation simplicity is afforded greater import than interface simplicity. Gabriel's article was widely read in the software engineering community and has since influenced a generation of programmers.

Discussions

If the best and the worst papers never appear together, then six examination papers can be arranged in how many ways?A) 120B) 480C) 240D) None of these

Complete step by step answer: Total ... Therefore, there are 480 ways in which 6 examination papers can be arranged where the worst and best papers never appear together. So, option (B) is correct.... More on vedantu.com

vedantu.com

March 3, 2025

If the best and the worst paper never appear together, then six examination papers can be arranged in how many ways

If the best and the worst paper never appear together, then six examination papers can be arranged in how many ways (A) 120 (B) 480 (C) 240 (D) None o More on tardigrade.in

tardigrade.in

167

April 2, 2021

Worse is better

"Worse is better" in language design means that everyone will be stuck with the poor decisions made 50 years ago, as demonstrated by countless examples. Do better. More on reddit.com

r/ProgrammingLanguages

November 9, 2022

The Rise of "Worse is Better'' (original source of the idea... not what I expected given usage)

tl;dr "Worse is better" is not an excuse to write bad software, it is an excuse to push complexity to the user after you've thought very hard about being able to solve it.

I think "Worse is better" suffers from being poorly named. Which is also what makes it so popular. Most people I talk to think that "Worse is better" is an excuse for making poor quality software because people like it. But that is wrong. "Worse is better" is about making a conscious decision as to where to put complexity and the cost-analysis of hiding complexity from the user. The MIT folks were stagnating because they couldn't solve a really hard problem in a way that they liked, but refused to leak that complexity to the user. NJ said that this is a hard problem, so we won't try to solve it on our end. While the NJ solution is worse, in that it leaks complexity to the user, it is also great in that you can always solve it later and remove that complexity from the user again. That let them move ahead.