The eternal holy war: Tabs vs. Spaces
Description
A four-panel comic by 'THE JENKINS COMIC' personifying the 'tabs vs. spaces' debate. In the first panel, a character in a trench coat stands before a nightclub named 'TAB CLUB', guarded by a bouncer who is a literal Tab key character. The second panel shows the character inside, mingling with other Tab key patrons, starting to say, 'So I said put it on my--'. The third panel shows the club's lights flashing red with a warning: 'INDENTATION ERROR DETECTED'. In the final panel, the Tab key bouncer throws the character out, revealing him to be four 'space' key characters stacked on top of each other. The bouncer says, 'Get out.' This comic humorously visualizes the conflict between using tab characters versus space characters for code indentation. In languages like Python, mixing tabs and spaces can lead to an `IndentationError`, a syntax error that stops the program from running. The meme is highly relatable to developers, as this debate is a long-standing 'holy war' in the programming community
Comments
7Comment deleted
That's what you get for not using an editor with 'convert tabs to spaces' enabled. It's the software equivalent of a fake ID
Spaces trying to pass as a tab is the nightclub version of a 3 AM commit titled “quick whitespace fix” - looks fine until the CI bouncer flashes INDENTATION ERROR and the on-call pager lights up
After 20 years in tech, I've seen teams split over microservices vs monoliths, but nothing creates lasting organizational trauma quite like discovering your principal engineer committed a .editorconfig file with 'indent_style = tab' during the company's IPO roadshow
The real tragedy here isn't the indentation error - it's that after 20 years of heated debates, we've collectively spent more engineering hours arguing about tabs vs spaces than it would have taken to rewrite the entire Linux kernel in Brainfuck. At least the Tab Club has standards; they'll throw you out for mixing whitespace, unlike that one legacy Python 2.7 codebase we all pretend doesn't exist where someone used tabs, spaces, AND non-breaking spaces because they copy-pasted from a Word document
Python's parser as Tab Club bouncer: mixes tabs and spaces? Straight to IndentationError - no cover charge refunds
Nothing exposes four spaces in a trench coat faster than Python’s parser - it’s the only bouncer stricter than our pre-commit
Tabs Club runs zero‑trust: the moment a space sneaks in, Python lights “IndentationError,” CI calls security, and you’re paged before finishing “put it on my - ”