Outside of the naming - this is a perfectly sane thing to do for developer comfort and can usually be accomplished with simple transformations.
replyThere are often limitations (like manually added indentation/spacing for alignment) but as long as you're very intentional about what changes you'll allow and have a good understanding of the language it can be an extremely safe operation.
I think git’s naming is actually pretty reasonable: smudge (on checkout) & clean (on stage).
replyIf he didn't bother formatting code, it would seem impossible to create a tool that formatted code the way he preferred.
replySounds like he did format code, and even had opinions on how it should be formatted, but OP disagreed.
replyreminds me of rob pike mentioning gofmt's style is "no one's favorite"
replyHaving K&R brackets be a syntactical requirement and everything else is a syntax error is okay with me though.
replyK&R, ride or die.
replyI find a lot of these conflicts I can't resolve when everybody agrees that the pain of ugly/unnecessary diffs is greater than the pain of minor formatting disagreements.
replyThis kind of passive-aggressive bullshit is exactly what's wrong with tech. People don't decide things: they just passively resist, and authority ends up being a muddle of truncated information flows.
replyIf someone sharing an old war story with what I felt was a positive and joking tone triggered you this bad, I feel bad for anyone working with you.
replyNothing in tech is worth going through life miserable. Nothing.
[dead]
reply