Berin Loritsch has a post discussing various aspects of efficiency of programming languages. He concludes with:
What I find most important is effeciency of maintenance. That means that the system should be self-explanatory, and provide enough information to be easily debugged. While creating a system as efficiently as possible is a concern, it is the poor maintenance guy that has to bear the brunt of the work. The easier it is for someone new on a team to get up to speed, the better the system is defined. Reducing the amount of code needed to describe a problem, and making it easy to understand what code performs which function are two very important ideals to pursue.
This is good advice that I think also applies to decisions about frameworks and application architectures. I’m taking a bit of a gamble, having never communicated with him (except in reading his blog), but I think that using the list of attributes from my previous post (Talk about the tradeoffs), he would place approachability and maintainability at the top of his priority list for teams in addition to when selecting programming languages.