Ignoring MDN's Warnings About Deprecated HTML
Description
A two-part meme combining a fictional dialogue with the 'Blinking White Guy' reaction image. The top section displays a Discord-style chat conversation between 'MDN' (Mozilla Developer Network) and 'Me'. MDN advises against using a deprecated HTML tag. 'Me' argues that it works and is still supported by browsers. MDN explains that browser support is only maintained due to continued use and that developers should collectively stop using it. 'Me' responds by simply writing '*uses the tag*'. The bottom section of the meme shows the 'Blinking White Guy' GIF, a popular reaction image of a man blinking in disbelief and mild annoyance. This perfectly captures MDN's exasperation. The humor resonates with experienced developers who understand the tension between following best practices (avoiding deprecated features) and the pragmatic reality of using what works, especially when browser support remains widespread. It's a classic case of 'do as I say, not as I do' in the world of web development
Comments
7Comment deleted
Using a deprecated tag is like casting a pointer to void*. It solves your immediate problem, but now you have to pray the runtime doesn't decide to segfault your entire career
When MDN begs us to drop <marquee>, I just rename it to .component-live-stream-v2 and the architecture board congratulates me on “leveraging proven code” - apparently deprecation is just a namespace problem
Twenty years from now, we'll still be supporting that deprecated tag because removing it would break half the internet, including three government websites, a Fortune 500's main portal, and that one internal tool everyone's afraid to touch because the original developer left in 2003
This perfectly captures the web platform's greatest feature and biggest curse: nothing ever truly dies. We're all collectively maintaining a museum where the exhibits still run in production, and every 'deprecated' sign is really just a suggestion that everyone - including browser vendors - politely ignores. It's the only industry where 'this will be removed in the future' has meant 'this will be supported forever' for the past 25 years. The real kicker? Those deprecated tags often have better cross-browser support than the modern replacements we're supposed to use instead
Deprecated HTML tags: browsers keep them alive longer than our best refactoring intentions
MDN: “deprecated.” Me: “deadline.” Web‑compat: “guess it’s immortal.” Deprecation on the web isn’t a lifecycle, it’s a pension plan for quirks mode
The web's deprecation policy is a garbage collector with no sweep - everything survives under web-compat