3 ms·
The appeal to needing better tooling is reasonable, but why should the results of the tooling be hard-coded into the text file? I don't have a great answer, but
by baddox 12y ago
The appeal to needing better tooling is reasonable, but why should the results of the tooling be hard-coded into the text file? I don't have a great answer, but basically anything you want to do with the presentation of source code can be done anywhere in the stack. Your editor could non-destructively display a series of variable assignments with vertically aligned values like the author prefers. And of course, on the author's side of the argument, git can show diffs ignoring whitespace.
It seems like the best solution is for everyone on a project to agree to some canonical representation to be hard-coded in the source files and versioned. What that canonical representation actually is isn't super relevant, although I would prefer something easy to read in plain uformatted mono space, for places like GitHub where developers probably don't have presentational tooling in place. What's important is that the canonical representation is agreed upon. It could even be enforced by shared git hooks. Then each developer can use their client side tooling to display the code in any presentation they please.