One way to characterize software is to think of it as a compression of the near-infinite into a finite space. You have at every point in the use of a program a good number of parallel paths you could choose. Some of these paths could arguably be unrolled and stored on a disk this big, instead of determining the value at run time.
For some calculations, it's very speed sensitive, so slow drive access would potentially eliminate this sort of size-speed tradeoff.
Slashdot Mirror
One way to characterize software is to think of it as a compression of the near-infinite into a finite space. You have at every point in the use of a program a good number of parallel paths you could choose. Some of these paths could arguably be unrolled and stored on a disk this big, instead of determining the value at run time.
For some calculations, it's very speed sensitive, so slow drive access would potentially eliminate this sort of size-speed tradeoff.