Hacker News Reader

Except gofmt and many others make the single most boneheaded formatting mistake - aligned indents. Aligned indents will cause a single-line change to balloon into a many-line diff, solely to re-align with the new content's length. This causes all sorts of unnecessary merge/rebase conflicts.

In my years of working with Go in multiple teams that was never really a problem and I haven't even thought about that once so far.

I wonder to what extent you've had to maintain stable branches then.

Still, if people are going to enforce something as meaningless as formatting, why not at least get it right? Otherwise it's unarguably just about stroking the obsessive compulsive tendencies of the team members who are more that way inclined.

> coding standards

Coding standards for NASA certainly isn’t bike shedding, especially if they focus on reliability or security

NASA effectively enforces a DSL, not coding standards.

Code formatting, quality metrics, and style guide/standards are all different things.