4 ms·
> Developers need fast IO (I have slow compile times, but I rarely desire a new CPU to fix that). Compile times are almost always CPU-bound. Put all your code
by aianus 10y ago
> Developers need fast IO (I have slow compile times, but I rarely desire a new CPU to fix that).
Compile times are almost always CPU-bound. Put all your code and headers/libs on a ramdisk [0] and hit compile and see how much faster it is. My bet is, not much.
[0] https://www.jamescoyle.net/how-to/943-create-a-ram-disk-in-linux https://www.jamescoyle.net/how-to/943-create-a-ram-disk-in-l... (just an example)
- interpol_p 10y agoI acknowledged compile times are CPU bound. I'm just saying that I'll take fast IO over faster compile times any day, for development. I want any data I access to appear instantly. Compilation often happens in the background and only very occasionally does it specifically block me from working. Slow IO, however, used to block me from working constantly.