I can't speak for the OP, but I've met people who "don't get it" for various reasons (me included at some point). I'm pretty sure the OP has heard this argument before.
Telling someone to use language A because it's much better than language B that the person is comfortable with is not a very good approach. You can get into the objective reasons as to why but for some it might be difficult to really understand.
I struggled with this when I was introduced to types as the entire concept was completely new to me. I had other ways I could think of to reduce errors (tests, more robust code, etc) and I wasn't sure how typescript could help me reduce errors any further or if it was worth learning a new (seemingly difficult) concept to deal with something I already felt I could deal with.
> I had other ways I could think of to reduce errors (tests, more robust code, etc)
You can still do that with TypeScript and also get type checks, null checks, and just typos found for you by the compiler. Why wouldn't you want the compiler to do that for you? I don't want to do it, I want the tools to do it.
Telling someone to use language A because it's much better than language B that the person is comfortable with is not a very good approach. You can get into the objective reasons as to why but for some it might be difficult to really understand.
I struggled with this when I was introduced to types as the entire concept was completely new to me. I had other ways I could think of to reduce errors (tests, more robust code, etc) and I wasn't sure how typescript could help me reduce errors any further or if it was worth learning a new (seemingly difficult) concept to deal with something I already felt I could deal with.