Originally Posted By: drakino

I wonder what impact this will have on overall application design. So much time seems to be spent across the computing stack managing caches and other tricks to deal with speed bottlenecks somewhere.
What will 'memory leak' means when the operating memory is the same thing as storage memory? The OS and programming implications are far reaching when 'rebooting' does not mean reloading 'main memory' from a known stable/blank state.

There are operating systems (and their apps) that live entirely within the machine memory for long run durations but aren't those mostly specialized and/or carefully managed application cases?