Yes, I did. What's the correct denominator that makes the daily effort worthwhile for you? Would you do x/5? x/10? x/50? After 50 days of continuously spending more effort than necessary, do you make the trade or just accept the ever-increasing loss of productivity? Fortunately for us all, the real number for "configure Typescript" is a lot closer to 1 than to 50.
Typescript is not saving me x/2 of the usual time I spend coding, not even close, not even in the ballpark. It's more like costing me 10% of my time due to missing types in libraries, hassle of extra tooling, more complexity, compilation step, etc, etc. Yes, I made that up that 10% figure, but I wouldn't be surprised if it's close to that.
If you're prone to making easy to avoid errors in your code, then maybe Typescript will save you time. For me, that is not the case. YMMV.
You don't think a tool saving 10% of your time is worth learning to use?!
Anyway, this gets off-track. The metric is (time wasted on problems that only exist without typing) / (time it takes to configure TypeScript). Regardless of what your 10% figure is, learning TypeScript and configuring it for a project takes less time.
> If you're prone to making easy to avoid errors in your code, then maybe Typescript will save you time. For me, that is not the case. YMMV.
Putting aside the dig, it sounds like you're working alone, so use whatever you want. It matters a lot less when you control the data structures and hold the entire program in your own head.
If you're a library author doing non-trivial type stuff, it's believable you might be slowed down by more than 10% because TS can get really really tricky for libraries.
But it's worth it because you're about to get a massive multiplier effect based on the scale of your user base.
>If you're a library author doing non-trivial type stuff
So what if I'm not a "library author", what I do could still be non-trivial, and I could still do it without typescript like people have been doing for decades before. Typescript is not the only strong-typing game in javascript town.
>But it's worth it because you're about to get a massive multiplier effect based on the scale of your user base.
Using typescript is not a causal factor for this. What the library does, and what people need is.
And honestly I don't care who is using a library I make, life isn't all about likes and it isn't a popularity contest.
