I used to be a fan of the idea, but over time I formed the opinion that "ordinary" software is just too error-prone to be worthy of full orthogonal persistence and life-long up-times. Tunes was supposed to be based on a high-level type-safe, memory-safe language runtime — but that would just be the least requirement. IMHO, formal methods and proof-carrying code (or some other novel idea altogether) would have to be applied throughout to avoid errors that would persist.
Orthogonal persistence has got an up-swing in academia in recent years after the introduction of new non-volatile memory tech, such as 3D CrossPoint. But I think that some of these researchers have applied it a bit naïvely. The best NVRAM is still much less reliable than DRAM, so it still needs e.g. wear-levelling and error-correction (and even write-throttling) — like what modern file-system stacks do.
Orthogonal persistence has got an up-swing in academia in recent years after the introduction of new non-volatile memory tech, such as 3D CrossPoint. But I think that some of these researchers have applied it a bit naïvely. The best NVRAM is still much less reliable than DRAM, so it still needs e.g. wear-levelling and error-correction (and even write-throttling) — like what modern file-system stacks do.