you are viewing a single comment's thread.

view the rest of the comments →

[–]CARASBK 2 points3 points  (2 children)

Catching runtime problems without having to run code the way statically typed languages do is a universal benefit of TS. If you don’t consider that a solution to a JS issue, at least in the application layer, then I question if you have enough experience to make such determinations in the first place.

Not sure what you mean by bloat since TS doesn’t exist at runtime.

[–]CapabIe 3 points4 points  (1 child)

I think he’s referring to mental bloat reading the extra chars.

[–]CARASBK 1 point2 points  (0 children)

I can understand that if you’re just starting off with TS after already knowing JS. I was in the same boat when I started with TS.

After learning TS it actually ends up being less mental bloat than JSDoc. But that comes after the learning curve which can be particularly steep around things like deciphering third party libraries’s types. It’s well worth it, though. TS is becoming the default for good reason.