3 ms·
The other problem with it is that it assumes that people have visible whitespace on, and that their tools even have that option to show whitespace, otherwise it
by zarzavat 3y ago
The other problem with it is that it assumes that people have visible whitespace on, and that their tools even have that option to show whitespace, otherwise it’s like navigating the Fuchsia Gym.
I don’t mind if people use tabs but mixing the two is not great.
- yetihehe 3y agoThe worst mixing I've seen: aligning on 4 spaces, but using tabs as a placeholder for 8 spaces. So first stop is 4 spaces, then tab, then tab and 4 spaces. Chaotic evil version of tabs vs spaces battle.
- yencabulator 3y agoWhy would you care about the whitespace? Formatting is a job for computers, not humans. I'm practically unable to `git add` unformatted Go or Rust code, and very happy with the setup: .config/git/attributes: *.go filter=gofmt *.cgo filter=gofmt *.rs filter=rustfmt .config/git/config: [filter "gofmt"] clean = "gofmt" [filter "rustfmt"] clean = "rustfmt --edition=2021"
- zarzavat 3y agoI’m not sure what relevance this has to files that use a mix of tabs and spaces because I’m not aware of any formatting tool that can reproduce that convention. Knowing whether a space in a space-formatted document is for alignment or indentation is AI complete.
- yencabulator 3y agoThe relevance is that I the human don't bother and the tools do it right. Go code uses both tabs and spaces...