Worse is better
Worse is better (also called the New Jersey style) is a term conceived by Richard P. Gabriel in an essay of the same name to describe the dynamics of software acceptance. It refers to the argument that software quality does not necessarily increase with functionality: that there is a point where less functionality ("worse") is a preferable option ("better") in terms of practicality and usability. Software that is limited, but simple to use, may be more appealing to the user and market than the reverse.
As to the oxymoronic title, Gabriel calls it a caricature, declaring the style bad in comparison with "The Right Thing". However he also states that "it has better survival characteristics than the-right-thing" development style and is superior to the "MIT Approach" with which he contrasted it.
The essay was included into the 1994 book The UNIX-HATERS Handbook, and has been referred to as the origin of the notion of a conceptual split between developers on the east and west coasts of the United States.
Gabriel was a Lisp programmer when he formulated the concept in 1989, presenting it in his essay "Lisp: Good News, Bad News, How to Win Big". A section of the article, titled "The Rise of 'Worse is Better'", was widely disseminated beginning in 1991, after Jamie Zawinski found it in Gabriel's files at Lucid Inc. and emailed it to friends and colleagues.
New Jersey style
In The Rise of Worse is Better, Gabriel identified a "Worse is Better" (also the "New Jersey style" or "east coast") model of software design and implementation which has the characteristics (in approximately descending order of importance):
- The design must be simple, both in implementation and interface. It is more important for the implementation to be simple than the interface. Simplicity is the most important consideration in a design.
- The design should be correct in all observable aspects. It is slightly better to be simple than correct.
- The design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either complexity or inconsistency in the implementation.
- The design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. In fact, completeness must be sacrificed whenever implementation simplicity is jeopardized. Consistency can be sacrificed to achieve completeness if simplicity is retained; especially worthless is consistency of interface.
The MIT approach
- The design must be simple, both in implementation and interface. It is more important for the interface to be simple than the implementation.
- The design must be correct in all observable aspects. Incorrectness is simply not allowed.
- The design must be consistent. A design is allowed to be slightly less simple and less complete to avoid inconsistency. Consistency is as important as correctness.
- The design must cover as many important situations as is practical. All reasonably expected cases must be covered. Simplicity is not allowed to overly reduce completeness.
Gabriel argued that "Worse is better" produced more successful software than the MIT approach: As long as the initial program is basically good, it will take much less time and effort to implement initially and it will be easier to adapt to new situations. Porting software to new machines, for example, becomes far easier this way. Thus its use will spread rapidly, long before a program developed using the MIT approach has a chance to be developed and deployed (first-mover advantage). Once it has spread, there will be pressure to improve its functionality, but users have already been conditioned to accept "worse" rather than the "right thing":
Therefore, the worse-is-better software first will gain acceptance, second will condition its users to expect less, and third will be improved to a point that is almost the right thing. In concrete terms, even though Lisp compilers in 1987 were about as good as C compilers, there are many more compiler experts who want to make C compilers better than want to make Lisp compilers better.
Gabriel credits Jamie Zawinski for excerpting the worse-is-better sections of "Lisp: Good News, Bad News, How to Win Big" and e-mailing them to his friends at Carnegie Mellon University, who sent them to their friends at Bell Labs, "who sent them to their friends everywhere." He apparently connected these ideas to those of Richard Stallman and saw related ideas that are important in the design philosophy of Unix, and more generally in the open-source movement, both of which were central to the development of Linux.
In December 2000 Gabriel answered his earlier essay with one titled Worse Is Better Is Worse under the pseudonym Nickieben Bourbaki (an allusion to Nicolas Bourbaki), while also penning Is Worse Really Better?, applying the concept to C++'s success in the field of object-oriented programming despite the existence of more elegant languages designed around the concept.
- Gresham's Law
- Less is more
- Minimum viable product
- Perfect is the enemy of good
- Progressive disclosure
- Rule of least power
- Worse is Better vs. Better is Better
- Worse Is Better, Richard P. Gabriel
- Worse is Worse, Jim Waldo, Sun Microsystems engineer
- Lisp: Good News, Bad News, How to Win Big, Richard P. Gabriel
- Daniel Weinreb. "The "Worse is Better" idea and the future of Lisp". Archived from the original on June 11, 2009.
- Worse Is Better Is Worse (PDF), Richard P. Gabriel as "Nickieben Bourbaki"
- Is Worse Really Better, Richard P. Gabriel
- Kreinin, Yossi (August 11, 2012). "What "Worse is Better vs The Right Thing" is really about". Proper Fixation. Retrieved 2018-11-24.