 |
A System Built to Die
|
|---|
| Wed Apr 25, 2001 | 2:33P| PermaLink |
|
|
"Like automobiles and appliances, I'm convinced that planned obsolescence is being woven into software so that it is designed or instructed to fail when the next version is marketed. During software design, tentative plans are often rejected because they tend to put the software into a less stable mode. Examples are options, add-ons, plug-ins and other functions that increase the complexity of the system without adding much value. The design process gives the manufacturer knowledge of ways in which systems can be destabilized."
|
|
FULL STORY @
OSOPINION
(http://www.osopinion.com/perl/story/9171.html)
|
|
|
