Comment by chris_armstrong
2 months ago
Might I add - this isn't limited to languages like TypeScript which simply try and make underlying untyped languages (like JavaScript) safer. It affects well-designed strongly-and-statically-typed-from-the-ground-up languages which have expressive type-constructs (Rust, anything ML-based, etc.) used to reduce repetition and code-generation steps.
Javascript is not untyped; it's dynamically typed.
In this context untyped means that it is dynamically typed and doesn't have static type hints. It's a fairly new word but I've seen it used enough and the meaning is obvious enough that I don't think you need to pedantically correct it.
I think if you want to talk about typing disciplines, and their trade offs, it's helpful to get basic definitions correct.
If I wrote something and I made a mistake like this I would hope someone would correct me.
3 replies →
This is true to some degree, but something about javascript/TS seem to lead to just incomprehensible typings. Imo any types where you start having to look at the keys of some map is going to lead to pain, but most other languages don't let you do that.