this post was submitted on 22 Nov 2023
215 points (92.2% liked)

Programmer Humor

19503 readers
1265 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
215
the myth of type safety (lemmy.world)
submitted 11 months ago by Zangoose@lemmy.world to c/programmer_humor@programming.dev
20 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Knusper@feddit.de 2 points 11 months ago (1 children)

I imagine what they mean is e.g. that TypeScript can tell you something is a Date, but it doesn't attempt to fix some of the confusing, quirky behaviour with that: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date#interpretation_of_two-digit_years

So, yes, it's generally better than JS, but it doesn't actually make it good/attractive, if you're used to the sanity of backend languages. It very much feels like lipstick on a pig.

[โ€“] Zangoose@lemmy.world 2 points 11 months ago

Exactly this. I'd rather use TypeScript than regular JS, but I enjoy using almost any other statically-typed language more (except maybe C++) because TS has the potential to be just as bad as JS for codebases where it isn't being used correctly (this is true for other languages as well but it's usually a lot more obvious).

Not that it isn't possible to have good typescript code, but rather that code becomes a lot harder to maintain because of problems that could've been prevented at a language level (truthy/falsey logic, 'any' type being allowed by default rather than 'unknown,' etc)