From: "Tony Ingenoso" 

Large doesn't have to mean slow or needing vast memory.  This is where
design and architecture come into play as opposed to throwing a bunch of
random code into a sack and shaking it up.  Attention to data locality and
working set are critical.

OOP isn't even necessarily the problem - its sloppy/careless use of it by
amateurs that's the problem.

"Geo"  wrote in message
news:427cb0a5$1{at}w3.nls.net...
> "Tony Ingenoso"  wrote in message
> news:427c0203$1{at}w3.nls.net...
>
> > Its really just admitting that code sucks and there's nothing we can do
> > about it 
>
> I think it's more of a question. Were we better off with 50K programs hand
> coded in asm and run on a 1mhz cpu or are we better off with reusable
module
> bloated programs that fill a 600mb CD and run on a 3ghz cpu?
>
> Geo.

--- BBBS/NT v4.01 Flag-5