Antifeatures: Difference between revisions
From WikiDotMako
(add the template for others to add) |
No edit summary |
||
| Line 1: | Line 1: | ||
Antifeatures are a way to describe a particular practice made possible by locked down technologies. Antifeatures, as I describe them, are functionality (i.e., "features) that a technology developer will charge users not to include. You can read [http://www.fsf.org/bulletin/2007/fall/antifeatures/ my short article on the topic]published in the FSF bulletin in 2007] for a series of examples and a more in-depth description. | |||
One thing I want to do is put together as large a collection of these antifeatures as possible to use in a talk, a paper, or maybe even a book! | |||
== Add Yours == | == Add Yours == | ||
Revision as of 17:29, 2 November 2009
Antifeatures are a way to describe a particular practice made possible by locked down technologies. Antifeatures, as I describe them, are functionality (i.e., "features) that a technology developer will charge users not to include. You can read my short article on the topicpublished in the FSF bulletin in 2007] for a series of examples and a more in-depth description.
One thing I want to do is put together as large a collection of these antifeatures as possible to use in a talk, a paper, or maybe even a book!
Add Yours
Feel free to add your own ideas for antifeatures to this page so I can collect them and use them in an upcoming talk, paper, or maybe even a book!
You can use the following template:
== NAME OF YOUR ANTIFEATURE == Change this paragraph so that it includes the details of your Antifeatures and any [http://example.com links].
