An introduction to type programming in TypeScript

Re:An introduction to type programming in TypeScript by mamcx on Wednesday February 02, 2022 @10:20AM (#30178749)

> but I find the complexity with the type system off-putting

Yeah, is it. But "complexity" is fine:

    Complex is better than complicated.
         - [Zend of python](https://www.python.org/dev/peps/pep-0020/)

What is a big trouble is when the complexity is NOT intentionally designed (ie: in languages like oCalm, Rust, Coq...) but instead the type system is a lie that bring "complications":

    //A bad language, like JS, with both complexity AND complications:
    [] - {}; // NaN

Humans can deal with complexity if is part of a intentional design (example: APL), but what we dread is when is accidental...

[ Parent | on HN ]

Re:An introduction to type programming in TypeScript by zkldi on Wednesday February 02, 2022 @10:28AM (#30178899)

    [] - {}

is a fatal typescript error[0]. A well configured linter can also catch out similar nonsense, but [] - 2 does get past the compiler.

The TS Compiler can atleast stop you from doing nonsense like applying operators to types where they don't make sense. Of course, it'd be better if JS just threw an error or something, but atleast TS can stop you.

[0]: The right-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type.ts(2363)

[ Parent | on HN ]

Re:An introduction to type programming in TypeScript by tomca32 on Wednesday February 02, 2022 @10:38AM (#30179058)

I’m curious about the example of unintentional complexity and type system lies in Rust?

Or did you mean to say that oCaml, Rust, and Coq have intentional design complexity?

[ Parent | on HN ]

Re:An introduction to type programming in TypeScript by mamcx on Wednesday February 02, 2022 @11:02PM (#30188491)

> have intentional design complexity?

yes, more like this (in special Rust, that deal with many challenges like system programming, safety, etc).

[ Parent | on HN ]