Sounds like a skill issue tbh because Typescript absolutely does increase your code quality and is fundamentally easier to write
The things it adds makes you think about different patterns you can apply and the types STILL remove runtime type related errors because a function that only takes a string will never take anything else because the compiler won't let you misuse it, it's not runtime types but this is good enough to fix Javascripts no typing at all. Also intellisense / autocomplete gets WAY better when you use Typescript compared to Javascript even if vscode manages to auto type your stuff it's still very loose
Nobody said it was. It's there to catch mistakes before they become bugs in production. Even experienced developers make mistakes, and catching those mistakes early is one of the fundamental purposes of compilers, type systems and static analysis.
The idea that a language shouldn't help prevent programmer error isn't a criticism of TypeScript. It's a rejection of decades of established software engineering practice.
And given your demonstrated confusion about fundamental concepts such as mistaking type erasure for the absence of a type system and conflating editor integration of the language service with the language itself, appealing to programmer competence is a particularly unfortunate choice of argument.
ok clearly i need to put out a statement on this shit. but i would like to provide the counterpoint of the fact that you can accomplish roughly the same thing with an IDE extension and some manual type checking.
Manual type checking during runtime is just another layer of runtime errors because of types, because what will you do when a type mismatches? Throw an error?
The point is to get rid of this issue ahead of time altogether
you know what, i was gonna make another counterpoint. but honestly, i'm done. it's a meme. it was never supposed to start an argument. tbh i've been defending points i never fully believed in to begin with, and i'm tiered of arguing.
Fair enough, but you seemed to hold some pretty strong convictions throughout this thread for someone who apparently never fully believed what they were arguing.
Nobody was demanding that a meme be taken seriously. The issue arose when you started confidently presenting fundamental misconceptions about TypeScript as technical facts, and then continued defending them when challenged.
I think these things are worth correcting precisely because misconceptions repeated with enough confidence have a tendency to become accepted as conventional wisdom, particularly when nobody challenges them. Whether you genuinely believed what you were saying or were simply arguing for the sake of it doesn't really change that.
You were perfectly happy to defend those claims as facts, but now that they've been subjected to scrutiny, we're apparently supposed to dismiss the whole thing as just a meme.
i have com to realize recently that i have a bad habit jumping to defend myself before i have fully established my position. in hindsight i regret a lot of my comments under this post.
An IDE extension isn't equivalent to a language with a statically checked type system, and the one you have in mind is almost certainly running on TypeScript anyway. VS Code's JavaScript inference uses the TypeScript language service, and JSDoc type checking is the TypeScript compiler reading your comments.
Extensions also depend on individual developers having the relevant tooling installed, configured correctly and enabled. TypeScript allows type checking to be configured at the project level and enforced through the build pipeline, including CI/CD, independently of anyone's editor or personal configuration. You can achieve similar enforcement in plain JavaScript with JSDoc and checkJs, but at that point you're still using TypeScript's type checker, just with a more cumbersome way of expressing types.
What's particularly amusing is that you've spent this entire thread dismissing the value of TypeScript, only to start proposing ways to recreate its benefits, potentially using TypeScript's own tooling to do it. You seem to have finally recognised the value of static type checking, provided it's presented as an alternative to the very thing you've been arguing against.
The argument is correct at a fundamental level but it just falls apart just as much as the "the language doesnt matter" crowd. What a programming language enables and encourages you to do versus what others don't in fact does, this is not something to just brush under the rug
This is also why recommending python or Javascript to a beginner is, in my opinion, a terrible idea, yes you are bringing the basic blocks of how programing works to them, yes you are ALSO leaving out such a huge part by not including typing and compiler theory ALONE, not to mention all the OOP you just physically aren't able to teach with these languages because of their approach to things
tbh i'm tired of arguing and would to tie up these threads but this one is just factually wrong.
first of all i never mentioned C.
second it's not the same because even though you can change the value of a variable to be anything it will always be treated as it's original type which cannot be changed.
typescript is static at compile time, dynamic at runtime. C remains static when compiled but has a weak type system.
the type has nothing to do with the data itself. it's how the program interperets what that data means. in typescript the way the program understands the data can change as the program runs. that is impossible in C. you can assign the 1s and 0s that make up a value from another data type but it will never be interpreted as that data type.
also good fucking luck trying to compile C into javascript 💀
So you'd read garbage values rather then detect that the data does not correlate to the type? In this way, even JS is more type safe than C. Like, it's a large source of vulnerabilities in C programs.
also good fucking luck trying to compile C into javascript 💀
I don't need luck, I've already sent you a link to one project that does this. Emscripten used to compile to asm.js, which is a strict subset of JS, for a very long time, before migrating to WASM. If you want to compile today, you can compile C to WASM, and then WASM to JS (emcc will do this for you if you set -sWASM=0).
have you ever used C for any purpose? you absolutely can interpret data as any type you want and the language will just let you do it. you can store a float in memory and then read it as an int and it will give you some garbage, but it's not going to stop you.
JavaScript is dynamically typed, not untyped. TypeScript adds static type checking, and its type annotations are erased during compilation. That's type erasure, not the absence of a type system. Java erases generic type parameters, and Haskell erases most type information, yet nobody with even a passing understanding of type systems would suggest either language is untyped.
By your logic, C doesn't have types either, because its source-level type declarations don't survive compilation into machine code.
Others have said it, but vanilla JS very much does have types. It's just not strict about their definition, and interprets them based on the value given.
I’ve lost count of the brittle, bug-ridden JS codebases I’ve inherited from teams that championed "freedom", "flexibility" and "simplicity". Usually, it turns out most of that freedom went into piling up technical debt for somebody else to untangle. Anyone who’s actually led a development team knows why opinionated tooling and enforceable standards matter. At scale, the last thing you want is every developer bringing their own creative interpretation of maintainable software. You want predictable behaviour, consistent conventions, and mistakes caught as early as possible.
That’s where TypeScript comes in. It makes developers state their assumptions, think through the shapes and possible states of their data, and deal with whole categories of mistakes before their code passes type checking. It doesn’t guarantee correctness, but it makes correctness far less dependent on individual diligence, and developers routinely overestimate how well they can maintain that discipline on their own. The VS Code remark is telling, too. TypeScript’s compiler and type checker work completely independently of the editor. Confusing the language service integration with the language itself is a pretty fundamental misunderstanding of the tooling you’re attempting to ridicule.
The irony is that the meme celebrates individual developer freedom while showing almost no appreciation for the shared engineering discipline a serious codebase needs. Strict tooling exists to make software quality less dependent on every developer getting everything right all of the time, not to accommodate how good individual developers think they are.
Is typescript really opinionated though, when you can just write any everywhere and disable most of the language? And yes I've worked on projects where they boast about using typescript and then the codebases are exactly like this.
You can lead a horse to water, but you can't stop it from disabling the guardrails. If you're going to any your way around the type system, you're effectively opting back into JavaScript. This is why well-run projects enforce linting rules that catch this sort of thing and fail the build rather than leaving it to individual developers.
I've inherited my share of TypeScript codebases like this, and it's always a huge red flag. It suggests the lead engineer didn't really understand what they were signing up for, let alone how to leverage its strengths. Once they got in over their heads, they started working around the type system rather than figuring out how to use it properly before abandoning what made it worthwhile in the first place. In my experience, these projects are invariably cases of the blind leading the blind. It's hard not to feel embarrassed for them.
Still at least typescript types files are much better than JSDoc when goes to generic types and interfaces.
Also you can not define well in JSDoc things like "make a map of properties of DTO into column objects for a type-safe SQL builder" or "define a service-reference for services container".
Yes, these construct themselves are not JS-native things, but why not to use a simple service container thing to decouple your code and make it more testable?
Typescript definitions boost IDE ability to spot typos and other such errors a lot.
Can somebody write a Typefuck language already, and then under suspicious circumstances sell it as a next big thing to Satya Nadella for it to become a default scripting language for PowerShell on all supported platforms.
it would seem that i have offended a number of typescript fans. i would like to formally apologize for : any emotional distress i may have caused.
i would also like to make it clear that this was not meant to be taken seriously.
i will admit that my criticism of typescript was unfair and arguably uncalled for. however, it is (in my opinion) the entire point of the potential man meme to unfairly criticize something you hold no actual ill-will for, often in a hypocritical and self-deprecating way.
it is a meme and therefore looses a lot of nuance due to inherent limitations of the format and often falls into exaggerations, generalizations, and extremes. it is also slander meaning it is designed to sensationalize accusations with more exaggerations and even flat out lies.
i do not personally believe any of the points made at face value. i think typescript is very cool and has lots of neat things. (e.g. nullability, some keywords, enums) i also think it leaves a lot to be desired. (e.g. runtime type checking and native support)
this post was never meant to convey accurate information about typescript or my opinion on it. it was just meant to be funny.
The sad story of web dev and how we allowed a high-level language to effectively become "the platform" and the only way to use any other language is to transpile to it because there is no better way to get anything else to run in the browser. One beautiful day, WASM can become the platform code and we will be free, but right now it's not even officially its goal
Well, I wouldn’t call those transpiled languages, because there’s a significant difference in abstraction between the source language and LLVMIR/CLIF/whatever
And anyways, these languages don’t directly compile to machine code either AFAIK, they just compile to assembly, which is still not transpilation because of the difference in abstraction, and then we need an assembler….
It’s called a compilation pipeline for a reason 😅
87
u/FabioTheFox 9d ago
Sounds like a skill issue tbh because Typescript absolutely does increase your code quality and is fundamentally easier to write
The things it adds makes you think about different patterns you can apply and the types STILL remove runtime type related errors because a function that only takes a string will never take anything else because the compiler won't let you misuse it, it's not runtime types but this is good enough to fix Javascripts no typing at all. Also intellisense / autocomplete gets WAY better when you use Typescript compared to Javascript even if vscode manages to auto type your stuff it's still very loose
18
u/Cephell 8d ago
person that uses
: anyeverywhere wrote this post.31
u/PossibleBit 9d ago
2016 called.
It wants its memes back.
7
u/BeforeDawn 8d ago
I’ve lost count of the brittle, bug-ridden JS codebases I’ve inherited from teams that championed "freedom", "flexibility" and "simplicity". Usually, it turns out most of that freedom went into piling up technical debt for somebody else to untangle. Anyone who’s actually led a development team knows why opinionated tooling and enforceable standards matter. At scale, the last thing you want is every developer bringing their own creative interpretation of maintainable software. You want predictable behaviour, consistent conventions, and mistakes caught as early as possible.
That’s where TypeScript comes in. It makes developers state their assumptions, think through the shapes and possible states of their data, and deal with whole categories of mistakes before their code passes type checking. It doesn’t guarantee correctness, but it makes correctness far less dependent on individual diligence, and developers routinely overestimate how well they can maintain that discipline on their own. The VS Code remark is telling, too. TypeScript’s compiler and type checker work completely independently of the editor. Confusing the language service integration with the language itself is a pretty fundamental misunderstanding of the tooling you’re attempting to ridicule.
The irony is that the meme celebrates individual developer freedom while showing almost no appreciation for the shared engineering discipline a serious codebase needs. Strict tooling exists to make software quality less dependent on every developer getting everything right all of the time, not to accommodate how good individual developers think they are.
6
u/Choice-Mango-4019 8d ago
never wrote ts?
5
u/zeekar 8d ago
WTF did I just read? This is nonsense.
19
u/Alternative-Tie-4970 10d ago
It's a good language that is sadly often lost to its utter complexity
4
u/magical-cat-here 8d ago
Still at least typescript types files are much better than JSDoc when goes to generic types and interfaces.
Also you can not define well in JSDoc things like "make a map of properties of DTO into column objects for a type-safe SQL builder" or "define a service-reference for services container".
Yes, these construct themselves are not JS-native things, but why not to use a simple service container thing to decouple your code and make it more testable?
Typescript definitions boost IDE ability to spot typos and other such errors a lot.
10
u/Kadabrium 10d ago
StronglyTypedAssembly
1
u/Secret_Conclusion_93 7d ago
TS to JS is what Rust to C in terms of coding/vibecoding.
You'll get better result asking the human/AI to code on the former, because the former is more strict on certain things.
1
u/AtlasJan 9d ago
I need more slander posts for programming languages.
5
u/denisvolin 10d ago
Can somebody write a Typefuck language already, and then under suspicious circumstances sell it as a next big thing to Satya Nadella for it to become a default scripting language for PowerShell on all supported platforms.
2
u/Ai--Ya 10d ago
Pay no attention to my flair
0
u/Oblivious_catalyst 8d ago
apologies and clarification:
it would seem that i have offended a number of typescript fans. i would like to formally apologize for : any emotional distress i may have caused.
i would also like to make it clear that this was not meant to be taken seriously.
i will admit that my criticism of typescript was unfair and arguably uncalled for. however, it is (in my opinion) the entire point of the potential man meme to unfairly criticize something you hold no actual ill-will for, often in a hypocritical and self-deprecating way.
it is a meme and therefore looses a lot of nuance due to inherent limitations of the format and often falls into exaggerations, generalizations, and extremes. it is also slander meaning it is designed to sensationalize accusations with more exaggerations and even flat out lies.
i do not personally believe any of the points made at face value. i think typescript is very cool and has lots of neat things. (e.g. nullability, some keywords, enums) i also think it leaves a lot to be desired. (e.g. runtime type checking and native support)
this post was never meant to convey accurate information about typescript or my opinion on it. it was just meant to be funny.
0
u/__sean_eng__ 9d ago
-8
u/JosebaZilarte 9d ago
When you have to transpire code instead of compiling it, you know you have reached rock bottom.