@sun typescript doesn't even have strong typing, developers themselves said that goal of language is to be a compromise between convenience and type safety. Problem with that is that typescript fails at both. You get types that suck ass and when you try to improve them you end up being sucked into a black hole and somehow come out of it realizing that no, you can't do good types where you wanted because typescript can't do that. You end up doing shit like as any as YourType, and at that point might as well not use typescript at all because your types become very fragile. Take shot every time you used a JS library with provided TS type definitions and realize that type definitions are outright WRONG. This is especially true for anything that is fetch()'d

It's all just busy work, wasted time that could have been spent writing JSDoc and comments in code. Bonus points to that because unlike TS typedefs/error messages those are human readable and are meant to be like that.