2 ms·
> For large, long-lived codebases, where there have been effectively many different teams and a number of different managers, the standards, coding styles, and
by quotemstr 10y ago
> For large, long-lived codebases, where there have been effectively many different teams and a number of different managers, the standards, coding styles, and tooling are almost certain to change
Sure, but I've never been convinced consistency matters at that scale. I think it's enough to be locally consistent; Windows doesn't seem to be hurt by its codebase containing practically every style you can imagine.
> level of the language community
Sure, but if you make the language too Procrustean, you risk making that community smaller, even if it's more cohesive. Personally, I'd rather have a bigger community, even if the members don't agree on everything.
- stcredzero 10y agoSure, but I've never been convinced consistency matters at that scale. I think it's enough to be locally consistent In C++, it can result in the occasional memory management paradox to work through. (In addition to the background cognitive load for watching out for such.)