Bit By Bit: Microsoft Destroys Decades-Old Hierarchical Scoped Settings
Microsoft Destroys Decades-Old Hierarchical Scoped Settings For over four decades, Microsoft built its empire on a foundation of consistency, reliability, end-user trust. There is an established hierarchical configuration model that has been in place for years and adopted by the entire software industry. The scenario is simple, a machine level (top) layer of settings meant to be applied consistently to all. This developer works with several clients, each with different requirements in their application, so without disturbing the configuration of any other project, he makes the adjustments to the solution layer. Now to add complexity but certainly a common situation, one project manager in this solution has his own requirements. The developer creates another configuration file with the new requirements. This is a perfect example of a typical large-scale project, not an edge case exception. If there is a setting in the lower level (project) that exists in a higher (machine) level...