I disagree. I work in an industry where unneeded and unused functionality is anathema - and will prevent certification of the system containing the software. Adaptive reuse - using the design as a template for the construction of a tailored solution - is a better alternative in my industry.
Technology cannot eliminate the difference in requirements for different applications.
Hmmm. Smells like avionics or process control.
I was around when "software reuse" became the big buzzword and Ada was introduced as a measure (in part) to reduce software development cost in increasingly computerized military systems. It didn't really work at the time, but it felt good to a lot of manager types.
The problem is identifying what is the difference between hard real time requirements (and I only define "hard" as in if you miss taking action and someone will get killed or injured or something is damaged or destroyed, but that's not the standard definition) and just keeping the system usable.
Technology cannot eliminate the difference in requirements for different applications.
I have to agree, much as I am in love with the idea of software reuse. However, I would like to s/cannot eliminate/has not yet eliminated/. I'm an optimist. I may not live to solve it, but perhaps one of my sons will. One thing that my reading in history has convinced me of is "never misunderestimate the power of the human mind".