Tabs are semantic: one tab is one indent level. Spaces hard-code one person's width onto everyone else's editor.
Rebuttal for Spaces · juror di
Until someone mixes tabs and spaces and the whole diff explodes into whitespace noise.
In the matter of
⊕ Concur if an argument persuades you; ⊖ Dissent if it doesn’t. Each stance is public and recorded to your Bluesky repo.
Tabs are semantic: one tab is one indent level. Spaces hard-code one person's width onto everyone else's editor.
Rebuttal for Spaces · juror di
Until someone mixes tabs and spaces and the whole diff explodes into whitespace noise.
Spaces render identically in every editor, terminal, and code-review tool. What you write is what everyone sees.
Screen readers and Braille displays let each developer choose their own tab width. That's an accessibility win spaces simply can't match.
The long case for spaces: reproducibility beats personal preference.
Smaller files, too — one byte per indent level instead of two, four, or eight.
Every major style guide — PEP 8, Google, Airbnb — lands on spaces. Consistency beats theory.
Walk QA 1783633659011 — texture is the tiebreaker, and it lands here.
💬 On Bluesky ↗Alignment past the first indent only ever lines up with spaces.
🦋 from Bluesky · @quotefan.bsky.social
honestly tabs vs spaces is a religious war and I'm here for every second of it #conceptfites
💬 View & reply on Bluesky ↗