https://news.ycombinator.com/item?id=46266102

一位工程师的回复：

A few things I've come to personally believe after spending years developing web and robotics software in Python/JavaScript then spending years having to maintain while constantly adding new features and dealing with company pivots:

• The types exist whether you write them down or not.
• If they're not written down, they're written down in your head.
• Your head is very volatile and hard for others to access.
• Typing is an incredibly good form of documentation.
• JSDoc and TypeScript are standards/formats for typing. Like any tools, they both have advantages and disadvantages. Neither is objectively better than the other.
• Make informed decisions on how you'll describe your types, and then be consistent and unsurprising.
• A type checker is the computer saying, "okay then, prove it" about your program's type validity.
• Not every program benefits from the same amount of "prove it."
• Too much can be as bad as too little. You're wasting resources proving throwaway code.
• I like languages that let you decide how much you need to "prove it."

翻译：

经过多年用 Python/JavaScript 开发 Web 和机器人软件、以及在不断新增特性、应对公司方向调整时负责维护这些代码后，我个人的一些体会：

• 无论你是否写下来，类型始终都存在。
• 如果你没把类型写成文档，那它们其实都记在你脑子里。
• 你的大脑极其容易遗忘，而且别人很难读取你的想法。
• 类型标注是一种极佳的文档形式。
• JSDoc 和 TypeScript 是描述类型的标准和格式。像所有工具一样，它们各有优缺点，没有哪一个绝对好于另一个。
• 要对如何描述类型做出有根据的决策，并保持一致性和可预期性。
• 类型检查器其实就是计算机对你说：“那好，请你证明下你的程序类型是对的。”
• 并不是每个程序都需要同样严格的“证明”。
• 太多类型验证和太少一样，都不好。你可能会浪费时间去验证一些一次性代码。
• 我喜欢那些可以让你自己决定“需要证明到什么程度”的编程语言。