The Unending Holy War: A 'Tabs vs Spaces' Meme Template
Description
A blank 'Drake Hotline Bling' meme template presented in a four-panel grid. The top of the image has a bold, white-on-black title that reads 'TABS VS SPACES'. The left column features the two standard Drake reactions: in the top panel, Drake looks displeased and holds up a hand in rejection; in the bottom panel, he smiles with approval. The right column contains two empty white boxes, corresponding to each of Drake's reactions. This meme is a template, inviting developers to fill in the blanks to state their preference in the eternal and often heated 'tabs versus spaces' debate - one of the most persistent 'holy wars' in the programming community. It humorously sets the stage for a discussion about code indentation and formatting standards without taking a side, allowing the viewer to project their own allegiance
Comments
13Comment deleted
The 'Tabs vs Spaces' debate is the senior developer's equivalent of a crypto flame war: endlessly passionate, ultimately pointless, and completely solved by just letting Prettier handle it on commit
Drake rejecting: endless tabs-vs-spaces bike-sheds; Drake approving: a pre-commit formatter that converts everything to spaces so every git blame line just says “ci-bot”
After 20 years in tech, I've learned the real answer to tabs vs spaces: it's whatever the linter auto-fixes to before the PR gets approved, because we're all too burned out from actual architectural decisions to care about whitespace anymore
After 40+ years of computing history, we've solved distributed consensus, built quantum computers, and landed rovers on Mars - yet somehow the tabs vs spaces debate remains our industry's most intractable problem. It's the only technical decision where both sides are simultaneously 100% correct and completely wrong, and where a single .editorconfig file could end the war but nobody wants peace
Tabs: flexible solo, catastrophic in collab when tab-width heresy strikes. Spaces: verbose but the only constant in a polyglot editor world
Architecture decision: tabs for indentation, spaces for alignment - until Prettier “helpfully” touches a Makefile and turns whitespace into an incident
Tabs vs spaces? We outsourced the decision to gofmt/black/prettier in CI; now the only bikeshed left is 100 vs 120 columns - until Makefile tabs collide with YAML spaces
pov you are developer using whitespace Comment deleted
reminds me of the nun that hosted the typewriter course in middle school. tabs vs. spaces was serious business back then Comment deleted
>CTRL+S >463 lines modified Your team must love you Comment deleted
thats why "ignore whitespace in diff" and "auto format on commit" Comment deleted
Settings -> Formatting Scope -> Modified Lines Only Comment deleted
Ctrl K Ctrl F Comment deleted