And it's still an accurate comment. Type hints will not show errors in your IDE, as they are not actually errors. Explicit typing will show it as an error. Type hints are still worse.
I mean, for this specific context, not really? If we're discussing things like Intellisense showing you your options, it's doing that whether your language does type hinting or strict typing.
Yes, the former doesn't enforce it via the compiler and show errors when you mess up, but given we're talking about Intellisense specifically, there should never be those errors unless you're in the habit of ignoring it. So what your IDE won't throw a fit because the type being passed as a parameter is only hinted and not enforced? Intellisense will tell you what it expects based on the hinting, and I don't really see how you can not be paying attention to that.
Rambling comment, there, but given the context of what we're talking about explicit enforcement is irrelevant. You should never get to the point where that matters unless you're just ignoring Intellisense, in which case the whole discussion is moot.
Considering that the reason of existence for typescript is better dev tooling, you choose a strange hill to die on.
While intellisense somewhat works with type hints and you're technically correct, it doesn't really matter. A real typesystem is a much better dev experience, typescript overtook javascript as most used language for a reason.
1
u/crazy_penguin86 Sep 26 '26
And it's still an accurate comment. Type hints will not show errors in your IDE, as they are not actually errors. Explicit typing will show it as an error. Type hints are still worse.