The existential dread of supporting Internet Explorer
Description
A meme presented in a tweet format from an account named 'SKILL IN PROGRAMMING' with a profile picture of Napoleon Dynamite. The tweet displays a conversation: 'client: and you've tested the site in internet explorer? me: ....yes.' Below the text is a well-known GIF of actor Jordan Peele sweating profusely, looking anxious and guilty. The humor stems from the shared trauma among web developers who have had to ensure website compatibility with Internet Explorer, a browser notorious for its non-standard rendering engine, CSS quirks, and JavaScript inconsistencies. The developer's lie is betrayed by their obvious panic, a feeling instantly recognizable to any seasoned developer who has been in a similar situation when asked about supporting legacy systems
Comments
7Comment deleted
I told the client 'Yes, it works in IE,' which technically is true if you count a 404 page with a 'Browser Not Supported' message as 'working'
Yes, we tested in IE - the user-agent triggers a 302 to a PDF titled “Legacy Support Surcharge.” All green on the dashboard
The real test isn't whether your site works in IE - it's whether you can maintain eye contact while claiming you've tested every combination of IE's 47 different document modes, ActiveX quirks, and that one VP's IE8 with compatibility view permanently enabled
The real skill in programming isn't writing cross-browser compatible code - it's maintaining a poker face when a client asks if you've tested in IE, knowing full well your CSS Grid layout and ES6 arrow functions are about to make their corporate intranet look like a Picasso painting rendered in Windows 95
That 'yes' hides three hours of conditional comments, box-model resets, and questioning your life choices in Quirks Mode
Our IE “support” is verifying the unsupported‑browser page is WCAG‑compliant and loads faster than the polyfills ever did
Tested in IE? Sure - ES5-only build, a museum of polyfills, no-flexbox CSS, and a prayer the corporate GPO doesn’t force Compatibility View; it finally passed once we shipped a second app