1
1. Implicit coercion isn't all that bad because once you understand it you can leverage it's power.
2. Javascript pseudo-classes aren't worth using because the code is hard to follow and they aren't real classes. Using "delegation-oriented design" patterns like Simpson's "objects linked to other objects" are more true to the essence of Javascript, and thus should be used.
Based on these two points it would make sense that Simpson isn't a fan of Typescript, which emphasizes strong types and classes.
The thing is...I can't remember a time where I really needed implicit coercion. And with Typescript making classes work more like traditional class oriented languages, what's the real problem?
Am I missing out on leveraging the "full power" of Javascript by choosing Typescript?
My grandfather is a retired electrical engineer who used to plan out and record progression on all his projects. He has boxes filled with his old notebooks. Is this just an old school take on project management and source control? Or do people find benefit in actual note taking during their projects? I've worked with dozens of programmers through out the years and I don't think I've ever seen someone approach it this way. I (briefly) attended one of the top IT schools, and outside of scratching pseudo code down on a napkin I don't recall it being practiced there either.