Principles
In 1984, Bob Scheifler and Jim Gettys set out the early principles of X:
- Do not add new functionality unless an implementor cannot complete a real application without it.
- It is as important to decide what a system is not as to decide what it is. Do not serve all the world's needs; rather, make the system extensible so that additional needs can be met in an upwardly compatible fashion.
- The only thing worse than generalizing from one example is generalizing from no examples at all.
- If a problem is not completely understood, it is probably best to provide no solution at all.
- If you can get 90 percent of the desired effect for 10 percent of the work, use the simpler solution. (See also Worse is better.)
- Isolate complexity as much as possible.
- Provide mechanism rather than policy. In particular, place user interface policy in the clients' hands.
The first principle was modified during the design of X11 to: "Do not add new functionality unless you know of some real application that will require it."
X has largely kept to these principles. The sample implementation is developed with a view to extension and improvement of the implementation, while remaining compatible with the original 1987 protocol.
Read more about this topic: X Servers
Famous quotes containing the word principles:
“When great changes occur in history, when great principles are involved, as a rule the majority are wrong.”
—Eugene V. Debs (1855–1926)
“The principles which men give to themselves end by overwhelming their noblest intentions.”
—Albert Camus (1913–1960)
“His principles are like the bristles of a domesticated pig, they don’t pierce through the pork.”
—Franz Grillparzer (1791–1872)