Nowadays, TypeScript is an industry standard, but the time has come to call it out.
For my whole developer career, I’ve been forced to use TypeScript because companies treat it like a religion.
But JavaScript was never meant to be a typed language; it is a dynamic, beautiful language, and not everything needs the overhead of TypeScript.
I know why it’s popular: it’s pure marketing and Bill Gates sick mind. He’s insane; he doesn’t want happy developers; he wants slaves to the compiler.
People shout that “TypeScript is for productivity and catching errors,” but I don’t want to waste hours catching unnecessary errors that TypeScript itself created.
If you want to talk about “efficiency,” let’s talk about how TS kills your machine.
While JavaScript is lightweight, the TypeScript compiler (tsc) is a bloated piece of shit that eats your RAM for breakfast. In any decent-sized project, the TypeScript Language Server (tsserver) will easily gobble up 3GB to 5GB of RAM just to tell you that you forgot a semicolon or that a type is “possibly undefined.” It turns a fast laptop into a space heater. You spend half your day waiting for the “red squiggly lines” to catch up with your typing.
That’s not productivity, that’s a prison.
The biggest lie is that TS makes production “safer.” It actually ruins it.
TypeScript is a ghost.
Once it’s compiled, it disappears. It provides zero protection at runtime.
You can have a “perfect” build that still crashes in production because the real-world data doesn’t match your imaginary interfaces.
It adds a massive, slow compilation step to your CI/CD pipeline.
You’re paying for server time and waiting 10 minutes for a build that should take 10 seconds in JS. It introduces “transpilation bugs” where the generated JavaScript doesn’t even behave the way the TypeScript source suggested.
JS is for frontend work, not backend.
This is why TypeScript stands out, because the backend needs a strict environment.
But come on, why choose Node for the backend anyway? It is a useless piece of shit.
I was a Node developer because my job forced me to learn it, and after trying Ruby on Rails and Elixir, I realized Node is awful.
Trying to “fix” Node by adding TypeScript is like putting a tuxedo on a pig; it’s still a pig, just harder to work with.
Stop forcing people to use TS. It is unnecessary. If you want to be a slave to the types, go ahead just leave us alone with our JavaScript. I love JavaScript. It was my first language, and it was perfect before they tried to turn it into a corporate nightmare.

Luka Tchelidze

A provocative critique of TypeScript arguing it's an unnecessary, resource-intensive layer forced on developers by corporate culture. The author claims TypeScript's compilation overhead slows development, consumes excessive RAM (3-5GB), provides no runtime safety, and bloats CI/CD pipelines. They advocate for JavaScript's dynamic nature and question the use of Node.js for backend development, suggesting alternatives like Ruby on Rails and Elixir instead.

Slaves to the Compiler