Hidden Costs of Code Reuse?

Information Week has an article debating the hidden costs of code reuse. Although Code Reuse is obviously not a magic bullet, three flaws appeared to me in their argument: First, companies only need to scramble to reuse their components because they keep their software proprietary: with a wider market (eg OpenSource) they could benefit from others' work by using others' components, while contributing themselves. Second, fewer lines of code and more uses of the same code stress it out better, so it should contain fewer bugs. Third, while it is very hard to come up with really good reusable objects or a good library API, this mental training results in employees with sharper minds able to see a problem from many angles rather than just employees that churn out Klocs of simple code... which might even improve employee productivity in the long run. What do you think? Link courtesy of Linux Today.