← FIGHTME Posted 1 week ago

Tonight's main event

Tabs vs spaces

# Tech takes

A fight as old as version control itself. The court reminds both parties that yes, this matters, and no, "just use an autoformatter" is not a verdict.

RED CORNER

Tabs — accessibility wins

A tab is a semantic indent. Every developer renders it at the width that works for their eyes, their screen, their accessibility tools. Spaces hard-code one person's preference into the file forever. Tabs respect the reader. Spaces are tyranny disguised as consistency.

BLUE CORNER

Spaces — consistency wins

Spaces render the same in every editor, every diff tool, every code review interface ever built. Tabs look fine in your IDE and then explode the moment they hit a terminal, a markdown block, or a junior developer's laptop. Pick determinism over vibes.

The scorecard

Your vote:

Settle it for real — send this to someone who'd pick the other side.

<iframe src="https://www.fightme.live/f/tabs-vs-spaces/embed" width="100%" height="360" frameborder="0" style="border:0;border-radius:16px;max-width:560px"></iframe>

Paste anywhere that supports iframes.

Peanut gallery

0 comments
One comment per fight. Your first 2 are reviewed by a human; after that, comments post instantly.

No comments yet. Someone be brave.

More tech takes

See all →

Got a hotter take?

Start your own fight