|
|
|
|
|
|
by sp332
3326 days ago
|
|
|
I think the interesting part is the programming model and not the amount of RAM. This computer has no separate storage area. If you want to manipulate data, you can do it in-place instead of reading it into a RAM-like working memory and then writing the result to a disk-like storage. |
|
|
You can already mount a filesytem backed by ram, or mmap files that exist on disk. What existing distinction between RAM and storage is holding anything back?
I see a reason some techniques will get more popular, but I don't really seen the difference. Saving a load operation? Not having to worry about flushing to long term storage? Am I missing something?