Not a Spring Onion on Nostr: Last week, I heard a compelling argument for using spaces (in your repo, not your ...
Last week, I heard a compelling argument for using spaces (in your repo, not your editor).
My position so far: Tabs are better, not because it saves memory, but because it's a semantic thing. Same reason why you don't commit build artifacts.
But: What if your developers are confused by indentation? Or unable to configure their editor properly?
Which makes a lot of sense depending on the people one is working with.
Published at
2026-01-25 10:13:36 UTCEvent JSON
{
"id": "54b28eeefd9ae6a2cf99013e7276bae0851b4c81f3cc0193d9392d0357200fbf",
"pubkey": "709e6828767535f31403097e685fbb8bdc7e90961ee3867b61aa6de38707b28a",
"created_at": 1769336016,
"kind": 1,
"tags": [
[
"proxy",
"https://tech.lgbt/@wakame/115955205148181035",
"web"
],
[
"content-warning",
"tabs vs spaces"
],
[
"proxy",
"https://tech.lgbt/users/wakame/statuses/115955205148181035",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://tech.lgbt/users/wakame/statuses/115955205148181035",
"pink.momostr"
],
[
"-"
]
],
"content": "Last week, I heard a compelling argument for using spaces (in your repo, not your editor).\n\nMy position so far: Tabs are better, not because it saves memory, but because it's a semantic thing. Same reason why you don't commit build artifacts.\n\nBut: What if your developers are confused by indentation? Or unable to configure their editor properly?\n\nWhich makes a lot of sense depending on the people one is working with.",
"sig": "7bb5789e76f6d2b5facbdfaccb09807591f4671ac05ee33742d8d64ce900519a35e69a54145928b696c3ee78fd383c84078665f24236473a7497d9aea1857cee"
}