> A story we collectively tell ourselves about it — how it should be used, which people it is for, etc. My personal opinion on this is that this is generally h

> A story we collectively tell ourselves about it — how it should be used, which people it is for, etc. My personal opinion on this is that this is generally harmful, as there will always be that one corner case which doesn't respect the "idiomatic" rules - and then you have to fight every time to explain the good reason which led these rules to not be respected in that place. I much prefer to say - any string valid in the language grammar is fair game ; if we don't want a string / construct / etc, then build a language in which the construct doesn't compile (or create a linter which fails the build, etc). Especially, you can't assume how other people learned the language - maybe someone went on C++ from LISP and builds his code around lambdas and std::function, or from Java and creates IAbstractObservableFactoryDispatchers by the dozen, or is a grammarian mostly experienced in Boost.Spirit or any other combination - that's ok, you're a dev, reading their code will enlighten you even if you need to google a bit, and open you to some paradigms which may later turn out to be the best fit for some use case of your code.