This is just a guess but I think that there are two problems here, not one: 1) inefficiency strictu sensu (more operations required for the exact same task), and 2) lower diminishing returns (that kitchen sink being included weights far more than the rest of the project, but maybe you should still not remove it because it still provides a small return of user utility).
In terms of resource consumption machine capacity has grown exponentially, but who can claim the same for user utility?
This is by now a problem so pervasive that even economists puzzle over (the missing information technology productivity gain)
But this text is part of the problem really, as it is too simplistic and doesnt feel like it identifies fundamental recipes for building better software