It works for "people" and "common sense".

All APIs need good documentation to be good APIs. If you're not providing good documentation with your API you're doing your users/consumers a disservice. Using a tool (TypeScript/Flow/whatever) to ease the pain of providing that documentation is in the best interests of an API developer since it reduces the friction of having to write the documentation by hand. Also, in this case, good documentation is not just documentation for the programmer that is consuming the API, but also the IDE within which the API is being consumed.

I'd say in this situation the title is justified.

All libraries should use input validation to avoid RCE and other attacks

All software that handles sensitive data should use transport encryption & encryption at rest

All software that uses encryption should use thoroughly vetted professional crypto

All computer users should use backup software

It's another click baity title like "Why we stopped using [popular X] for [less popular Y]", "[Popular X] considered harmful", "Why you shouldn't use [industry standard X]" etc.