3 ms·

Is there a way you can isolate the "reasons that are well known" into "reasons that can be made to work even in non-Typescript situations"? Or can the "reasons

Is there a way you can isolate the "reasons that are well known" into "reasons that can be made to work even in non-Typescript situations"? Or can the "reasons that are well known" be laid out for closer scrutiny and discussion? Is it possible that there are multiple paths up the "massively improved productivity" mountain? Any of these angles could help move the problem even further off the mark of "my subjective perceptions vs. theirs" and into the objective "our perceptions" zone through additional openness. If this can't be done I'd guess you'd run into a lot of problems that are more psychological in nature. Generally when you say "here's a great thing," (especially if others think they have great ideas also) you get a backlash effect at the very least.

nilia 5y ago
It is definitely psychological, and I'd say what I'm looking for is pretty much what you asked: good resources that explain all the advantages clearly and debunk the common misconceptions (which usually revolve around the idea that typescript will make it super slow and tedious to write code) It's very hard to bother people out of nowhere and spend time arguing with them about why they're wrong about TypeScript, and can seem confrontational. That's why it would be a lot easier if there were external resources or even sources of authority vouching for it and helping with people's insecurities around it I suppose. So what I'm really looking for is finding out what worked for other people. For example if there's a great talk/article/video/whatever that helped convince people easily, or even to use as a base to keep in mind a list of useful facts to mention to people (it's easy to forget when using it what people were thinking before then)