Re: if vs. when vs. and: style question

[Emanuel Berg]

Yesterday night I read this which illustrates my point
- it was posted on
gwene.org.slashdot.rss.slashdot.slashdot.book.reviews
- indeed, quite a mouthful, but the post is
straightforward:

    As with any content management system, building
    a website using Drupal typically requires
    extensive use of its administrative interface, as
    one navigates through its menus, fills out its
    forms, and reads the admin pages and notifications
    — or barely skims them, as they have likely been
    seen by the site builder countless times before.
    With the aim of avoiding this tedium, speeding up
    the process, and making it more programmatic,
    members of the Drupal community created a "shell"
    program, Drush, which allows one to perform most
    of these tasks on the command line. At this time,
    there is only one current print book that covers
    this tool, Drush for Developers, Second Edition,
    which is ostensibly an update of its predecessor,
    Drush User's Guide. Read below for the rest of
    Michael's review.

Here we see a clear chronology:

First there is a shell...

Then there is an editor...

That's all you need to do advanced things...

Some people think the advanced things are too
advanced, so they come up with a CMS (e.g., Drupal)

Now people think the CMS isn't advanced enough, so
they have came up with a shell, namely Drush!

You see what just happened? "If anything can start
anew, then everything must continue". Is it amazing,
a waste of time, or a combination thereof? And: Will
the Usenet community supply the answer?

-- 
underground experts united
http://user.it.uu.se/~embe8573