4 ms·

Typescript is great compared to plain JS, but they're really deep into diminishing returns area with type system features for a couple of years now. A lot less

Typescript is great compared to plain JS, but they're really deep into diminishing returns area with type system features for a couple of years now. A lot less would be a lot more, because as of now Typescript lures otherwise entirely competent programmers into writing complex 'type system puzzles' which are entirely obscure to everybody except the person who wrote that code, and it takes a lot of discipline and experience to reist the lure and keep things simple.

toastercat 4y ago
I feel similarly to this, and often find when working on a TypeScript codebase that I get "distracted" by spending more time trying to get my types just perfect.
pjmlp 4y ago
I kind of agree, some Typescript projects look like Haskell envy (with all GHC extensions enabled).
- hajile 4y ago
  The Haskell type system is WAY more simple than the type soup TS allows you to make. I'd gladly take Hindley-Milner typing and typeclasses (or better yet, module typeclasses) over the current TS situation.
  - pjmlp 4y ago
    I suggest a digression by GHC extensions.
hbrn 4y ago
I feel the same way, I lost amazing engineers to this weird typing obsession. Excessive typing is very costly and should be left to popular libraries that solve generic problems. This is where you get best bang for buck. It should not be present in your business code, high level business logic is rarely prone to type errors anyway. Static typing was always a means to an end, but unfortunately it was recently sold as a virtue and many people have bought it.
hajile 4y ago
TS shouldn't have embraced all the JS quirks. I want a type system that embraces the correct way to to do things instead of allowing anything you want no matter how bad it actually is. I want my type system to inform me that my code is really bad for performance and should be redone. Instead, I constantly deal with people who think their code is fine just because the TS checker doesn't complain.

toastercat 4y ago

I feel similarly to this, and often find when working on a TypeScript codebase that I get "distracted" by spending more time trying to get my types just perfect.

pjmlp 4y ago

I kind of agree, some Typescript projects look like Haskell envy (with all GHC extensions enabled).

hajile 4y ago
The Haskell type system is WAY more simple than the type soup TS allows you to make. I'd gladly take Hindley-Milner typing and typeclasses (or better yet, module typeclasses) over the current TS situation.
- pjmlp 4y ago
  I suggest a digression by GHC extensions.

hbrn 4y ago

I feel the same way, I lost amazing engineers to this weird typing obsession. Excessive typing is very costly and should be left to popular libraries that solve generic problems. This is where you get best bang for buck. It should not be present in your business code, high level business logic is rarely prone to type errors anyway. Static typing was always a means to an end, but unfortunately it was recently sold as a virtue and many people have bought it.

hajile 4y ago

TS shouldn't have embraced all the JS quirks. I want a type system that embraces the correct way to to do things instead of allowing anything you want no matter how bad it actually is. I want my type system to inform me that my code is really bad for performance and should be redone. Instead, I constantly deal with people who think their code is fine just because the TS checker doesn't complain.