> you either insist on it and say it's the only supported developer-environment-defining framework, or you will lose control over it That's true for any archit

> you either insist on it and say it's the only supported developer-environment-defining framework, or you will lose control over it That's true for any architectural decision in an organization with more than 1 person. It's really not something that should make you reconsider a decision. At the end of the day, an architecture that "people" actually want to use doesn't exist, "people" doesn't want any singular thing.