Exactly. After all, to make minor changes in tightly coupled systems, one often has to redesign much of it to get it all to work together again after that apparently minor change is made.
I'm even of the opinion that the performance benefits of tight coupling are mostly imaginary due to unforseen indirect consequences of tight coupling in large projects; when things need to be altered during development, sloppier fixes are encouraged by the difficulties created by tight coupling.
Of course, I'm far from the foremost expert in code modularity, and could well be out of my depth here.
|print substr("Just another Perl hacker", 0, -2);||- apotheon
CopyWrite Chad Perrin