curious wrote:
>
> pardon my stupidity..
> what will this planned management software do?
Not at ALL stupid. I'm FAR more interested in getting the specification
list and the design set done than in picking a language.
To be somewhat cliched: there's two types of programmer. Ahem.
One type:
Slow project development, designs to death, writes only after design is
complete. Project is true-to-specification, is usually compiled.
Other type:
Fast project development, 'prototype' design method, quick releases of
partial code. Project specification changes frequently, project is usually
interpreted.
At the moment, discussion appears to be dominated by the prototypers. Me,
I'm a designer.
And I still vote for a compiled language, and vote even more strongly
for 'so what do we want to make this do?' to be answered before we
pick a language,
I expect to be shouted down by the prototypers, though. Who will
/probably/ start writing what they think they want it to do, and
meld the bits of code together until they come up with something
which does their favoured jobs.
NB: Neither programming method is more correct than the other. Like different
languages, each has its uses.
NB2: So far, the arguments put forward for both Perl and Python don't appeal
to me. I don't /write/ that way.
Jenn V.
--
Humans are the only species to feed and house entirely separate species
for no reason other than the pleasure of their company. Why?
[EMAIL PROTECTED] Jenn Vesperman http://www.simegen.com/~jenn/
************
[EMAIL PROTECTED] http://www.linuxchix.org
