Semantic Purity vs. The Pragmatic `<br>` Tag
Description
A two-panel Wojak comic meme contrasting two developer mindsets. On the left, a crying, angry Wojak character with glasses and a yellow bow tie exclaims, 'Nooo!!1 you can't just add random line breaks. You have to use proper semantic elements'. This represents a strict, by-the-book approach to web development. On the right, a calm, smugly smiling, older-looking Wojak is shown next to the orange HTML5 logo. The caption below him reads, 'ha ha browser go <br><br>', representing a pragmatic, old-school developer who uses the simple line break tag to create vertical spacing, ignoring modern best practices. The humor lies in the conflict between frontend development purism (using CSS for layout) and the quick, 'dirty', but effective legacy method of just inserting line breaks. It's a classic 'rules vs. results' scenario that resonates with experienced developers
Comments
7Comment deleted
Sure, use semantic tags. But when the designer says 'nudge it down a smidge,' the browser understands `<br>` a lot faster than it understands a long-winded PR debate about design tokens
After a decade evangelizing semantic HTML, the highest-converting page in prod is still the one the sales guy built in Outlook with 42 stacked <br> tags - browser rendering: 1, my architectural dignity: 0
Twenty years in and I still ship <br><br> to production while my PR comments preach about semantic HTML - the only difference now is I've automated the hypocrisy with a linter I immediately disable
The eternal struggle: spending 3 hours architecting a perfectly semantic HTML structure with proper heading hierarchy, ARIA labels, and landmark regions, only to watch a contractor ship '<br><br><br>' for vertical spacing because 'it works in Chrome.' Meanwhile, your accessibility audit report grows longer than your sprint backlog, and the PM asks why the 'simple spacing fix' is taking so long to 'do it properly.'
If your spacing strategy is <br><br>, congratulations - you’ve invented whitespace-as-a-service with 0% WCAG uptime
Using <br> for layout is SELECT * for UI: it “works” until i18n expands the copy, screen readers narrate 17 line breaks, and every PR diff becomes a war of whitespace
Semantic HTML for the spec sheet, <br> for the sprint demo - browsers forgive, audits don't