> You need to be in it for the long run and you need to be utterly dedicated to make this really work. There also has to be an escape hatch to make this work.

> You need to be in it for the long run and you need to be utterly dedicated to make this really work. There also has to be an escape hatch to make this work. E.g., Linus can say that the __is_constexpr preprocessor hack is the product of a demented mind, and he'll merge that absolute monstrosity thanking the contributor. As a leader you get the contributor community that you get. You can either make the development process workable for them, or you can risk the project languishing/forking. Put another way: if a leader's concept of what their project ought to be/become veers too far from what the community is actively coding up to be merged, it's not going to go well. No idea if this applies to D. But I'm absolutely certain Python's dev process has had plenty of escape hatches for resolving development issues. (And I'd guess there are also projects that have too many escape hatches, but I'm guessing that probably doesn't apply to D.)