I came across a reasonably interesting question on Reddit today, ask "If you don't use TypeScript, tell me why (5 year follow up)".
Frustratingly it …

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

The post discusses why the author doesn't use TypeScript in their code, including difficulties with parsing, lack of documentation, and challenges in appeasing TypeScript. These issues are specific to the author's experience and may not apply to all developers.

Why my code isn't in TypeScript

Finally a post that doesn’t support typescript.
From the first moment I saw generics I knew that typescript wasn’t for me.
The cost that typescript brings to the code in terms of maintenance, readability and learning curve is very high, I don’t see clear benefits from its use.

<blockquote>
I spend more time trying to resolve TypeScript complaints than I do adding code
</blockquote>
The author has a strong point. I also want to spend more time on coding than solving TS-related issues.

If everyone is on the same boat with properly documenting with jsdoc then typescript will die one day