2 ms·
Keyboard typing is not a bottleneck. I always cringe when I hear people cry about long method names with those really big tears. I did find that build times d
by austin-cheney 1y ago
Keyboard typing is not a bottleneck. I always cringe when I hear people cry about long method names with those really big tears.
I did find that build times did impact my concentration during rapid experimentation or troubleshooting. When I first got into TypeScript my compile times were only 8 seconds. Then on a later dramatically larger project of around 100 files and greater than 50k lines of code my compile times got up to 30+ seconds. I switched to SWC and my compile times dropped to about 8 seconds before climbing back up to about 11 seconds. Now I am spending my time on a different project that is not as large and my compile times with SWC were about 3 seconds. I recently dumped SWC for the Node native TypeScript support and I have no compile step. It appears Node takes about 1.5 seconds to run its type stripper on my project into memory, and I am comfortable with that.
I know those sound small, but they still interrupt my concentration compared to the almost 0 time to just run a JavaScript run time. You also have to understand I am into extreme performance and can load this one app I wrote, the UI portion of an operating system, in the browser with full state restoration within 80ms of page request.
- 0x445442 1y ago30 seconds for 100 files sounds horrible. Was this time including tests?