I think your points are some of the best reasons to avoid TypeScript, but I still definitely prefer TypeScript. I think I just find the disadvantages less cumbe

I think your points are some of the best reasons to avoid TypeScript, but I still definitely prefer TypeScript. I think I just find the disadvantages less cumbersome and the advantages more compelling. Even though editors can give reasonable autocomplete for JS these days, I think there's a certain amount of trust and comfort that you lose, and I find it really nice to have little mistakes flagged right as I'm typing rather than when running the code (even when I have a fast iteration cycle). I also greatly prefer TypeScript when trying to use code I've never seen before, whether that's code written by someone else on my team or third-party code. The types add an extra layer of explanation that's hard to convey in docs or function/variable names. And as discussed separately, PropTypes is much better than nothing, but I think it has plenty of gaps, and I feel much more confident and comfortable in a codebase with full typechecking. (I didn't downvote; I upvoted you since I think your post is a good contribution to the discussion.)