RE: Don't overlook Simplicity.
- From: "Roger Vaughn" <rvaughn pobox com>
- To: "Gnome List" <gnome-list gnome org>
- Subject: RE: Don't overlook Simplicity.
- Date: Sat, 19 Jun 1999 09:16:14 -0400
> -----Original Message-----
> From: James Henstridge [mailto:james@daa.com.au]
>
> Making things simple to the end user is great for newbies, but quite often
> simplicity just gets in the way of the more experienced users (if you have
> used MS office, what did you think about the paper clip after the first
> two minutes?). If it is possible to create a simple interface that does
> not limit functionality for experience users, then that is great. It is
> not necessarily a good idea to go for simplicity where it limits
> functionality for more experienced users though.
>
There's one big mistake I keep seeing in this thread - don't confuse
Microsoft
with simplicity. They are a *horrible* model to follow. MS has a very bad
habit of making things very difficult to use by automating things too much,
and deciding that they know better than users how things should be done.
The
overwhelming trend in MS software is to take flexibility and configurability
*away* from the user completely. This isn't simplicity - this is
dictatorialism. (Wouldn't King Bill love that?)
SIMPLE software allows you to accomplish common task quickly, intuitively,
and
easily, without more steps than are necessary. At the same time, it cannot
prevent you from accomplishing things in different ways, or from
accomplishing
more complex tasks, if you wish to take the time to learn them. Proper
simple
software does not make the complex tasks difficult, either - they just may
not
be as readily apparent.
Qmail is a good example of simple but powerful software. With just a few
variables configured at installation, you can have it running. If you want
a more complex mail installation, it will let you do it.
Believe it or not, rebuilding the Linux kernel on most systems is also
simple
but powerful. "make config" is a very simple step that guides you line by
line
through all of the configuration variables. If you don't understand them
all,
fine. Just accept the defaults. Anyone can build a new kernel this way.
But
if you take the time to learn what all of the settings mean, you can
carefully
tune your kernel to your specific requirements.
Truly simple software is a difficult goal to achieve (user-friendly =
programmer-
hostile), but it's a worthy one.
rog
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]