> What limitations have been kept? For example: multiple address spaces. The disk/RAM dichotomy is an atrocity, along with everything it entails (i.e. files.)

> What limitations have been kept? For example: multiple address spaces. The disk/RAM dichotomy is an atrocity, along with everything it entails (i.e. files.) There is no reason for the machine to expose multiple address spaces. The act of program installation and loading into memory, for example, should be one and the same. Think "Palm Pilot." RAM is in practice simply a cache of disk, and for some reason we are stuck "driving stick" and moving things into and out of it by hand. Why can't we treat it the same as L0/L1 cache? > what do you suppose we should do? How about this: http://en.wikipedia.org/wiki/Persistence_(computer_science) http://en.wikipedia.org/wiki/Persistence_(computer_science) and, while we're at it, this: http://en.wikipedia.org/wiki/Genera_(operating_system) http://en.wikipedia.org/wiki/Genera_(operating_system) And, in general, (not) these: http://www.reddit.com/r/programming/comments/6gpwh/ask_reddit_what_atrocities_in_the_software_world/c03so2j http://www.reddit.com/r/programming/comments/6gpwh/ask_reddi...