| |||||||||||||
|
| |||||||||||||
Why customizability doesn't encourage wasting timeWhy customizability doesn't encourage wasting timePosted May 13, 2004 7:43 UTC (Thu) by simon_kitching (guest, #4874)In reply to: Why customizability doesn't encourage wasting time by janpla Parent article: Living Down to a Low Standard (ComputerWorld) I'm one of the people your comments are referring to :-). And if you look back at that earlier comment, I point out that there is a cost to providing those features. Every feature is a potential bug. It also sucks up developer time, tester time, documentation writer time, disk space, ram. So to me the best solution is to have multiple versions of the component (the window manager in most cases cited here). The basic, stable, simple, well-documented version is released as the base product. Users who want more features can install the more flexible (and potentially more buggy, larger, more difficult to use) version if they want. Voila - problem solved. And if there isn't enough interest in the developer/tester/documenter communities to support the more flexible version, then that's not a reason to complain to/about those developers who work on the base version. So why not install Enlightenment, Sawfish, or one of the other "advanced" window managers? Or get a community together, make some patches to the base Metacity and release Metacity+ for those who want it?
(Log in to post comments)
|
|
||||||||||||