> who insists on maintaining top-down control This is quite the opposite of what he insists on. He insists on good code, not control. He maintains control be

> who insists on maintaining top-down control This is quite the opposite of what he insists on. He insists on good code, not control. He maintains control because of the former. He went so far as to design git to avoid top-down control and make sure that anyone can fork the code at any time. The funny thing about the ARM "blow up" is that all the ARM devs for the most part agree with him. Things needed to change, he knew it and they knew it. He just provided the push.