Re:Ruining the diversity of JavaScript community with a codi...
by threeseed on Monday November 11, 2013 @05:37AM
(#6710931)
Coding styles can often be enforced through automated means before checkin. And even if they can't it is trivial to flatten commits to make style changes disappear.
The point of style guides are to leverage best practices and ensure anyone can easily read, understand and modify your code.
Adherence to a common style keeps such noise to a minimum, leaving you with a commit history that's full of meaningful changes rather than meaningless thrashing over whether to indent four characters or two, or whether the { goes on the same line as the if (...).