4 ms·
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 type
by 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.