> telling the computer how to run it took pretty much the same amount of typing, this time not in a programming language but in a structured markup language. T

> telling the computer how to run it took pretty much the same amount of typing, this time not in a programming language but in a structured markup language. The myopia of "how much code and config is in my app" is inefficient for code reviews, but weigh that against what you gain. Plenty of people use languages and frameworks without understanding the massive inefficiencies involved. With configuration, you get insight into some of that inefficiency. It's also more inefficient during code reviews to have to review N changes in configuration. But, is the end result fast enough for users and is the time needed to develop and maintain it sufficiently low? If the answer is yes, assuming you're a foot soldier in the dev brigade, you keep going. It's good to reduce the noise. Chuck Yeager started as a mechanic and worked on his own planes when he became a pilot. That made him a better pilot. But, James Hart Wyld was the one concerned about the efficiency of the engine. Chuck just needed to break the sound barrier without dying.