Yep, can relate. The irony is that most of those people who tend to over-praise TS are juniors and have never worked on a properly architected JS project. I can understand why people think that they've reached their peak performance and concluded that they'll always need training wheels on their bikes but, really, no Olympic-level cyclist would make that argument.

Many of the more dogmatic arguments in favor of TS are cope by people who prefer to embrace mediocrity by pretending that producing clean, reliable code without special aids is almost impossible, rather than admit that they have a lot of room left for self-improvement... And that no tool can substitute the value of self-improvement. TS is sometimes a convenient way to turn the page and make JS into a scapegoat for one's own past failures.

"Oh yeah, that project was a disaster but it wasn't my fault that the architecture was unmaintainable and that it mixed different types together and didn't do any schema validation; it was JavaScript's fault."

Give it a couple of years and the same people will be switching to Golang or Elixir and blaming Typescript for their failures. These people always need a tool to serve as either their hero or their scapegoat and that's also why they can never improve their skills beyond the point of mediocrity.

TS is useful for certain situations where the code is horrible or there aren’t enough senior developers on the team (for a complex project) but neither of these situations are desirable to begin with in my view.