> This is a superficial take. I've been using TypeScript in server-side, client-side, and hybrid projects for 8 years. Since then, I've inherited JS projects a

> This is a superficial take. I've been using TypeScript in server-side, client-side, and hybrid projects for 8 years. Since then, I've inherited JS projects and felt like I was being forced to use a rock when I was used to having hammers. My take isn't superficial. > You are adding a compilation step that takes time The entire project is compiled only when testing or deploying. As far as testing goes, having static types dramatically reduces the number of times you have to run a program before shipping it. The net is that there's less time waiting for builds, not more. And anyway, most projects compile in 2 seconds or less. There is a huge net time saving no matter how you look at it. > slowing down feedback in certain workflows This is incredibly vague. Which workflows? And why does it matter in those workflows? The majority of feedback given by TypeScript is during the editing process, and that feedback is instantaneous because it comes from the language server and doesn't require recompiling. > a rather large dependency No. It's a dev dependency and doesn't ship with your code. You have to install it locally at some point, so I guess if a few MB of space is important to you, it's a problem. Otherwise it isn't.