On Thu, May 8, 2008 at 1:47 AM, Charlie Kester <corky1951_AT_comcast.net> wrote:
> * Christoph Lohmann <20h_AT_r-36.net> [2008-05-07 23:48:20 +0200]:
> With respect, focusing on lines of code is the wrong perspective.
> It doesn't matter if you see that number as an achievement or as
> an expense.
>
> If you make reducing LOC your primary goal, you end up writing
> Python or Ruby.
>
> I want:
>
> - small executables - simple, clean user interfaces (do one thing and do it
> well) - good performance
>
> When measuring smallness, it's important to include any shared
> libraries or runtime environments in the calculation. Many Python
> programs are only superficially small. (You could say the same
> thing about a bash script in comparison to a Bourne shell script.)
My personal opinion has always been that focusing heavily on reducing
the number of lines of code is almost as misguided as maximising the
number of lines you produce. Taken beyond the sensible level of
removing functionality that doesn't belong at the level of your
application, you end up creating code that embodies so many _hidden_
assumptions and dependencies on how other parts are implemented that
it's very difficult to modify.
To my mind, a well designed application should have exactly the
functionality that is best implemented at its level, no more and
equally importantly no less. If that requires more lines of code then
that's a price worth paying.
-- cheers, dave tweed__________________________ david.tweed_AT_gmail.com Rm 124, School of Systems Engineering, University of Reading. "while having code so boring anyone can maintain it, use Python." -- attempted insult seen on slashdotReceived on Mon May 12 2008 - 10:34:53 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 15:38:41 UTC