This is great if you're using a loosely typed language (like JS), but I think the need for this is why things like Typescript are gaining in popularity. I used

This is great if you're using a loosely typed language (like JS), but I think the need for this is why things like Typescript are gaining in popularity. I used to love the eslint-enforced jsdoc in a repo I maintain, but since we embarked on a TS migration, it has become painfully redundant in 90%+ of cases (there are cases where the jsdoc contains extra commentary/context that TS doesn't cover, but I think those cases are covered by the author's other comment types). So given the above, I think it's notable that you are referring to JSDoc (and by extension JS) whereas the author is referring to Javadoc (and by extension Java). The language choice is particularly important here.