The Unrequited Respect of a TypeScript Developer
Description
A four-panel comic from 'poorlydrawnlines.com' depicting the relationship between JavaScript and TypeScript developers. In the first panel, two characters are shown; one holding a yellow 'JS' logo says, 'I LIKE JavaScript,' and the other, holding a blue 'TS' logo, replies, 'AND I PREFER TypeScript.' In the second panel, the JavaScript character begins to say, 'BUT WE STILL RESPECT EACH OTH - '. He is cut off in the third panel by the TypeScript character, who angrily shoves the JS logo away, yelling, 'GET THAT DIRTY BULLSHIT OUT OF MY FACE.' The final panel shows the dejected JavaScript character standing alone with the JS logo on his chest. The comic humorously exaggerates the zealotry sometimes found in the developer community, specifically satirizing the perception that many TypeScript developers, having embraced static typing, view vanilla JavaScript with disdain for its lack of type safety
Comments
7Comment deleted
A TypeScript developer sees 'any' and thinks, 'Ah, the devil's type signature. A legacy incantation from the dark ages before compilation.'
Kickoff: “JS and TS can totally coexist.” Week 3: code review devolves into a cage match over whether `unknown extends any ? never : string` is elegant type-safety or just Java in cosplay
The TypeScript developer's migration plan was perfect until they discovered half the team's "any" usage was actually a design pattern called "trust-driven development."
This perfectly captures the JS/TS discourse: we all claim to respect different tooling choices until someone suggests removing 'any' from the codebase, then suddenly it's a holy war about whether compile-time type checking is worth the cognitive overhead or just enterprise Java cosplay for the web
The JS - TS debate always ends the same: one side trusts the compiler, the other trusts prod to run static analysis via PagerDuty
TS: Because nothing says 'I respect JS' like rewriting it with types that vanish at runtime
Everyone’s neutral on JS vs TS - until someone sets 'strict': true at the repo root and npx tsc --noEmit dumps 4,000 compile‑time feelings into the PR