Fwd: Re: [arch-projects] Keeping the list alive!
mail at andy-roberts.net
Mon Aug 1 12:48:44 EDT 2005
I'll forward this for Rasat as he only sent it to me but I expect it was for
---------- Forwarded Message ----------
Subject: Re: [arch-projects] Keeping the list alive!
Date: Monday 01 Aug 2005 15:45
From: Rasatmakananda <rasat at pacific.net.sg>
To: Andy Roberts <mail at andy-roberts.net>
On Mon, 2005-08-01 at 15:19 +0000, Andy Roberts wrote:
> > .... the selection of
> > language is also part of Arch's concept of KISS.
> > http://bbs.archlinux.org/viewtopic.php?t=13576
> This is surely from a programmers perspective, i.e., languages that make
> programming easy. I really don't think that language choice was part of
> Judd's vision, since he's a C programmer.
Not Judd's vision but somehow the choice of C and Bash were the right
languages making Arch an ideal distro where users can easily hack and
configure as they want. This is the main factor in Arch. Not only a
product to use but anyone who is interested can easily develop on their
own or join in Arch development.
What I am trying to say here, most of the Archers are "devs" in one way
or other, or learn to become because of user contributions. Therefore
loves in products/projects what is simple in performance and easy to
help/hack for further improvement. If one sided, the language is too
troublesome to read/hack, they may still use the product but will not
The Arch Way:
"Don't let configure tools / GUIs control the system but be controlled
by the user".
In my recent understanding, this principle applies not only, not to be
controlled in configure matters but also not to be depended what tools
offer. A tool should be hackable to be able to makes things as user
want..... not what the tool want (smile).
More information about the arch-projects