From: kate rhodes <masukomi@...>
Date: 2006-05-03T06:18:55+09:00
Subject: Re: Sharp knives and glue

------=_Part_8175_30731334.1146604731456
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

having worked in perl and php and Java i have to say that when you're
working with inexperienced programers and / or programmers who just don't
care about doing things the right way flexible languages like perl, ruby,
and php are IMNSHO dangerous. It's far too easy to write crap code. When
there are 50 solutions to every problem people tend to use whatever works
instead of the best solution. These languages are great in that they're eas=
y
to get started programming with...but they suck in that they don't enforce
good habbits.

*IF* you can convince your team to actually use test driven development i
think that these languages would probably be fine, but if the problem is
that you're dealing with people who aren't using best practices to begin
with then I would have to say "Yes, go for Java". There are far fewer
solutions to every problem and thus far fewer stupid options.

Of course if you REALLY want to enforce good practices you might want to
look into languages like Eiffel with its static typing and enforcement of
design by contract. Then again... selling a project written in Eiffel to a
client is probably even harder than selling Ruby one.

-kate / masukomi

------=_Part_8175_30731334.1146604731456--