I took it to mean that the longer a popular module remains untouched, the more code out there relies on it. Over time, it may become clear that new techniques could improve the module. As long as nobody works on the module, it'll never be improved, and thus all code that relies on it doesn't get improved, either.
There is some software that covers its problem domain so well that nobody thinks of making substantial improvements on it. There's a reason why C is still considered the best language for writing operating systems. There's a reason why FORTRAN is still used for heavy number crunching in scientific applications (FORTRAN + DOS + memory manager + GHz processsor = very, very fast). However, I would bet that most such examples are exceptional cases.
"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.
In reply to Re^2: Simon Cozens' modules need you!
by hardburn
in thread Simon Cozens' modules need you!
by sintadil
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |