2 ms·
Alright, let's do some legit math here. Compile times are often about 15 minutes, so a 5% improvement would shave off 45 seconds. That's not too bad. But becaus
by 8n4vidtmkvmk 5y ago
Alright, let's do some legit math here. Compile times are often about 15 minutes, so a 5% improvement would shave off 45 seconds. That's not too bad. But because that's still a very long wait, I'm not gonna twiddle my thumbs for 14 minutes and 15 seconds, I'm going to go do something else. Probably some social site to kill a few minutes, maybe check some emails, who knows what. Then I'll come back 20-30 minutes later to check if my tests passed or failed. So that 45 seconds isn't really saving me anything because I've already moved onto other things. We have to get that down to a few seconds to avoid distractions. 15 minute / 1000 brings it down to less than a second.
And then my other point was that depending on my day, I might not be writing any code at all. For the past few weeks I've just been reading and writing documents. So no amount of speed improvements will help me.