Transcript from the "Validating Operand Types" Lesson
>> Kyle Simpson: One thing that I think is undervalued within TypeScript this is actually where many more of my bugs have come from. It's that in addition to being able to a static typing information about variable assignments, it can also tell us that certain operations would be invalid. In this particular case, it's saying you can't subtract a string from a number.
[00:00:21] Because that particular preference is saying don't allow that coercion, and in this particular case, that would be a really useful help for me. I would really like for a linter to tell me, don't try to subtract a string from a number. What I'd really like is a linter that let me have that, but not let me have all the complaints about all my static type assignments.
[00:00:41] That would be my preference. But this is, I think, an undervalued part of what they do. Is that they are actually allowing us to check the operations that we're doing where most of our business logic is, and making sure that those operations are valid. It would be nice if TypeScript would have some mechanism by which you could allow some more coercion to occur.
[00:01:03] Because there are plenty of places, as I've already made the case, where I'd like to be able to do coercion and other Places I'd like to avoid it. It appears to me in my research that Typescript is kind of all or nothing. You opt into it or you don't opt into it.
[00:01:17] I'd prefer there to be more nuance and configuration.