These are some valid points for sure. I also hated the overhead of typescript.

The reason we decided to use typescript was communication. Our team is going to grow, and we want to be able to communicate to eachother how our code is used (especially for new devs).

Yes, it's often a fight, yet that fight is usually up front work. Typing gets a lot easier when you've pushed passed the hard stuff (much of which will no longer be a problem when using the comp API).

Absolutely it can be more difficult to understand... Yet often we use typescript to make lower level concepts easier to consume. Make it clear what goes in and what comes out. So when consuming something well typed, it's actually a whole lot easier to understand.

So it's probably almost pointless for small projects with one developer (unless it's second nature to you). Immensely valuable as the project grows.

By the way... This is all personal experience with ONE large project, so I'm hardly a good source :p

As for the "sorcery". It's persistence. It's constantly searching for the answers and pushing to understand more.

Hello, TypeScript