4 ms·

Typescript users: LOVE IT! Non-typescript users: ANOTHER layer? /sigh/ Cynical, yes, but that's because I haven't had a smooth onramping experience the times

• celim307 7y ago
  When I introduce it to a new team, leaving js/jsx as valid and making TS optional is usually good enough. Whether through peeking at your TS code or just being curious, usually they come around, and if not, they are still responsible for their code. The tradeoff is theirs to make
• AgloeDreams 7y ago
  Using TS since ~2017. Moving an existing codebase to it is a giant pain, otherwise it's not bad. It fits you into better practices, but don't treat it as types are always true. When debugging issues I'll commonly assume Typescript's types do not exist or how it would act if they are wrong. This is notably true of consuming API responses with mixed data types. Generally, what I really like about typescript is that you normally blend it with linting, minifying, and strong IDE integrations. These things, when combined, really help code readability and adherence to TS conventions and eventually save you from massive bugs that might not have been caught prior. Obviously, at the end of the day, how you use it really defines how helpful it is. All that said, I haven't ever really had major issues with the tools around TS.