I freely admit that. I don't get it. AT ALL. Because it seems to be fear-mongering nonsense about problems I just don't encountier.

Like the mystical "runtime error" stuff that I don't see anything - - the way I write JS -- that typescript would, should, or even could prevent.

Or at least not for anything I'm not already handling.

I dunno, maybe all those years of writing Pascal, Modula 2, and Ada have ingrained into me not writing code that won't "make it past the compiler".

Since as the joke goes, when it comes to shooting yourself in the foot with Pascal, "The compiler won't let you shoot yourself in the foot" so I understand that aspect of it as "training wheels"... I just fail to even see where it ACTUALLY would do that in any decently written scripting. If it IS actually providing that, then you're dealing with some really shoddy coding.

But then 80%+ of the JS codebases I waltz into end up half their size or less by the time I leave. Less code you use, less there is to break. Just like all the crap jQuery, React, Angular, Vue, and Typescript coders seem to throw code at that isn't even any of JavaScripts business. Nothing like replacing 200 lines of JavaScript with three lines of CSS.