>Rust is an even more extreme example. You might get extra safety, but at significant development cost. I don't buy this argument. If you want your program to

>Rust is an even more extreme example. You might get extra safety, but at significant development cost. I don't buy this argument. If you want your program to do what you intend you have to know the types anyway. I've never spent significant time on finding the right type, even in Rust. I have spent significant time on incorrect code, because of functions that accepted inputs with the wrong type and didn't complain, because the wrong type had the same method. I have spent significant time on looking up what a function can do, because the IDE can't figure out what my parameter is. I have spent significant time on programs that ran into runtime problems every once in a blue moon that would have been easily detected by a good type system at compile time. Articles like this just show me that every language that needs to have maintainability for large projects will turn into strongly, statically typed at some point. Whether it's type hints or TypeScript.