You're right, 5x is probably an exaggeration. Maybe in practice it's more like 2x... Still that would be a lot. Often an iteration does literally take me 3 seco

You're right, 5x is probably an exaggeration. Maybe in practice it's more like 2x... Still that would be a lot. Often an iteration does literally take me 3 seconds; like if I just want to quickly log a variable to the console. I can find out in 2 seconds. Other times, if I made a small mistake it will take me less than 30 seconds to fix and test with JS. Most of my time coding is spent on very short iterations which are 30 seconds or less. I rarely encounter problems with type mismatches or wrongly named variables or that sort of thing (and when I do, my test case catches that even faster than a TS compiler would have)... Also, waiting for the compiler tends to break my train of thought. It's a distraction and it increases my anxiety levels because I end up spending most of my programming time anxiously waiting for a result - That's why it's not enjoyable. I hate this waiting time between when I implement the change and when I get to see the result. I think that even people who say that they like TypeScript will subconsciously feel more anxious while they're using TS. Waiting for results naturally creates anxiety; you want to minimize that time. I'm even thinking that maybe making employees feel anxious is part of the corporate agenda to keep them under control. Maybe they did some studies and found that TypeScript caused fewer employees to leave the company? Maybe it wasn't for the reasons they believed. Anxiety tends to make people more withdrawn, less confident and stay in jobs they hate.