> That's so fundamental to the type system that I think if you want to work around it, you might not fully understand how TypeScript works yet. I think most en

> That's so fundamental to the type system that I think if you want to work around it, you might not fully understand how TypeScript works yet. I think most engineers who use (and swear by) TypeScript don't fully understand how TypeScript works (or JavaScript for that matter). I've worked across multiple teams at multiple companies and always run into types I can't trust because they are just plain wrong and inconsistent with the runtime, or data that isn't typed correctly. I also found that everyone writes TS differently, and sometimes the verbose typings and weird non-idiomatic patterns introduced just to please tsc actually make the code harder to read (30-line JS modules become 120-line TS behemoths). I still prefer working with TS on teams (though I prefer JS on solo projects now), but after a while I ask "is this the best we can do?" /end minirant