The second step
Storage Class Memories will be upon us in a year or two, but there isn't serious discussion about the system implications of fast persistent storage. It won't be a case of just using it as a DRAM that doesn't lose memory. Operating systems don't recognize that type of memory, so a major change is needed here.
The applications are written around disk storage, and need a major rewrite to work with SCM, especially if word updating is supported.
All in all, the availability of the memories isn't going to be the pacing item, unless some action is begun on the software side. Having been involved in an SCM program, I understand the size of that mountain, and it isn't small! There are ways to get some functionality quickly, but the full potential of SCM requires changes to compilers, link editors, memory copy routines, machine check handlers, boot loaders, sleep routines, and the file IO system. A good model for SCM is an extended page memory, but that code predicates a slow disk save.