12 ms·
Starting Over: A FOSS proposal for a new type of OS for a new type of computer
- jarym 6y agoFor me at least this link breaks the browser back button and prevents me from coming back to HN (iOS Safari)
- boris 6y agoTo me things that are worth starting over would be the CPUs that we no longer understand and the OSes that are debugged into existence. Not a computer that has no SSD because memory is persistent.
- qayxc 6y agoBoth OSes and complex CPUs are a direct result of their capabilities. I'd wish physics would end at Newtonian mechanics and Maxwell equations, but alas special- and general relativity cannot be avoided in some circumstances and neither can quantum mechanics in others. The same is true for CPUs and operating systems - if you need high performance and the ability to do real-time high-resolution media playback, digital content creation, high-bandwidth networking, high-colour and high-resolution graphic displays with font smoothing, auto-scaling, multi-monitor support, pluggable peripherals, etc. etc. you'll get complexity. There's only so much that can be achieved with simple TTL and core memory... Microkernels and provably correct OSes are great and available, too. But things start to get messy quick once you add support for various protocols, devices, and capabilities. Not just because it gets harder and harder to do, but also because there's diminishing returns: the vast majority of users aren't OS developers and just don't care. The same way the vast majority of people don't care about the layout, build quality, and logical soundness of the plumbing in their homes (as long as it works sufficiently well) or the technical details of their refrigerator. That's why there's very little incentive to build small, "clean", and provably correct OSes for the general public. You will find them, though, and they are in use.
- loudmax 6y agoI applaud the drive and vision to experiment with a fundamentally different operating system paradigm. But even if your persistent storage is RAM, I don't see why you wouldn't still want a filesystem. Filesystems arose as a method of organizing data. However fast your access time, you still want that. Maybe you could have some kind of database backed tagging system instead of a directory hierarchy, but the benefits and drawbacks of such a system should apply to an SSD or even HDD as much as to something in RAM. This goes for user data (eg. photos, documents) as well the organization of the operating system. Anyway, I'm curious to see what what this project comes up with. I suspect it will be something that looks and functions a lot like a filesystem, but I'd be happy to be proven wrong.
- karmakaze 6y agoAdvances in performance are largely about impedance matching, from sequential access tapes to registers in a CPU. You want to use an efficient interface and abstraction for the level you're at. The direction of progress is toward faster, more randomly accessible with less seek cost: HDD -> SSD -> XPoint, etc. This totally makes sense--using RAM through a disk interface (e.g. RAM disk) is useful if you want a faster disk, to get something faster change the interface to take advantage of the medium.
- hderms 6y agoI think the main benefits would be rethinking the core of persistence to be more about atomic operations on datastructures as opposed to POSIX filesystem IO. I personally believe that files are still a useful metaphor, and this hypothetical OS that we're discussing would likely still provide them, at least for interop. An example being a database. Provided we didn't have to batch writes, be aware of dirty pages, write things in certain order to maintain coherence in the event of a crash, etc... we could build something really simple. Ultimately it would depend a lot on the details like memory bandwidth+latency between DRAM and NVRAM
- blackrock 6y agoEven AWS S3 is a key-value storage system. Meaning your key can be anything. But over time, people tend to name the key using a path structure, separated by forward slashes, to give a logical separation of data into subdirectories.
- agalunar 6y agoI've never used Multics myself, but from what I understand it was also based on the idea of mapping files in memory. When I first heard this, I thought the idea was pretty neat, but then the person I was speaking to remarked that it wasn't all that great in practice. I'm not really sure why, but I'm curious.
- tenebrisalietum 6y ago`mmap()` sucks if you don't have a lot of addresses. 64-bit computers now have a lot of addresses.
- agalunar 6y agoI'm skeptical this was the reason, though (at least in and of itself). Going off of https://en.wikipedia.org/wiki/Multics#Novel_ideas https://en.wikipedia.org/wiki/Multics#Novel_ideas, it seems that the address space (36 address bits ⇒ 36 bits/word × 2³⁶ ÷ 8 bits/byte = 288 GiB) was much larger than memory of the machine Multics was designed for (about 2 MB), and the size of a segment was limited to about 1 MB (36 bits/word × 2¹⁸ ÷ 8 bits/byte), nearly half of all memory – so I doubt this was troublesome at the time.
- moonbug 6y agobecause now you've turned failed IO operations from an errno into a segfault.
- egypturnash 6y agoI feel like I have so many problems with this. Like, look, I have some huge projects in Adobe Illustrator and they are quite deliberately spread out among a ton of files because anything over a certain size is just asking for working on it to become super-slow, and for some obscure edge case to completely trash the file. I'm skimming the PDF of his slides and I'm just seeing a long list of quirky environments that have continued to be dead-ends. Maybe he talks about how this would actually work with huge power tools if I watch the talk, maybe he grapples with issues like "programs crash" and "iterative backups are good". Maybe he even deals with things like "files are a metaphor based in the physical world and perhaps the reason we keep on coming back to them is because they provide a good way to say that this particular piece of information is over here". I dunno, I'm not seeing suggestions of anything that makes me want to invest the time in listening to the talk. I wish him the best of luck, maybe he will be the one to finally find a way out of the world of files to something so clearly better that it's worth dealing with the raw edges of it only being a few years old vs a modern GUI atop a filesystem, but I sure ain't gonna hold my breath.
- amw-zero 6y agoI can say this. I highly doubt we’re done innovating with how software is made. I feel like systems development has gone extremely out of fashion in the past couple decades. The OS’s and tools we have are good enough to get a lot of stuff done. However, there’s still quite a few problems, and we don’t even know the productivity level we could get to, because we haven’t seen the future. There’s nothing wrong with not being a dreamer or not trying wanting progress the industry. But, there’s also nothing wrong with doing those things either.
- lproven 6y ago[Author of the piece here] The slides are just decoration and can be safely ignored. You would be much better off reading the script: https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VRJ8OxpVdkzHxQF_8X5So/edit?usp=sharing https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VR...
- martinskou 6y agoI have had this thought about much web software these days. Requesting a lot of data from DB instead of just keeping a persistent object system in the memory.
- zokier 6y agoI went through the slides, saw bunch of pictures of old computers, but where is the proposal?
- isaacimagine 6y agoThe Google Doc has the proposal at the bottom. Basically, take the bottom half of Oberon and slap on the top half of Squeak*, bara-bim bara-boom - you've a next-gen OS. *Or SBCL + Dylan The whole schpiel is to make a high-level interactive OS / computing environment that straddles the line between interpreter and compiler. The whole is is run in-memory, and can be snapshotted and restored quickly. No filesystem, just RAM. Interesting idea, I guess :)
- lproven 6y ago[Author of the piece here] Thanks! I should have expected that so many people wouldn't listen or read it, just look at the pictures... >_<
- trasz 6y agoPersistent memory sounds whole lot like OS/400.
- s314159265358 6y agoDoesn't this almost say no to the con Neumann architecture? Is this a good idea? Isn't the point of having multiple files to simplify managment and reduce risk of corruption?
- qayxc 6y agoThe concepts are orthogonal. Von Neumann machines can be used without file systems and vice versa. Persistent state has its pros and cons - for me the ability to reset the machine's state is an important feature. For the author this doesn't seem to be the case. As for abandoning the concept of a file system, that's something that has been worked on for decades. Microsoft even wanted to include this as the main feature for Windows Vista, back in 2003 (dubbed "WinFS"). They basically wanted to replace traditional files with a single relational database backed by schemas for describing objects. This would've been a truly revolutionary concept, as it would've allowed for features like searching, sorting, grouping, and versioning of objects without any complex application-level code. Another advantage of such system would be the ability to exchange data between apps by just passing an id. All required meta-information would be available through the schema and the app could choose a view that suits its needs: providing the id of an audio file could result in the title and artist for a word processing program, the audio data for a music player, or the associated cover art in case of an image editing program. There are many options for replacing the concept of files and directories that are just as robust and provide extra features. The general architecture of the CPU is not affected by or related to this.
- tzs 6y agoThis part: > A possible next evolutionary step for computers is persistent memory: large capacity non-volatile main memory. With a few terabytes of nonvolatile RAM, who needs an SSD any more? I will sketch out a proposal for how to build an versatile, general-purpose OS for a computer that doesn't need or use filesystems or files, and how such a thing could be built from existing FOSS code and techniques, using lessons from systems that existed decades ago and which inspired the computers we use today. reminds me a bit of something I've long wanted to experiment with (or see someone else experiment with). Here's how I described it in a comment here on HN a while back [1]: > I've toyed with the idea of replacing files with processes. If you have some data that you want to keep, you have a process that holds it in its process memory, and can give it other process via an IPC mechanism (if the other process is local) or over the network (if remote, although you could of course also use the network locally). > I never got around to trying it out. I think I may have tried to start some discussion on usenet along these lines maybe 10-15 years ago, but no one seemed interested. > A "directory" would simply by a process that provides some kind of lookup service to let other processes find the data storage processes that contain the data they are looking for. > You'd still have disks on your computer, but they would be mostly used as swap space. > The system would include some standard simple data holding and directory processes that implement a Unix-like namespace and permission system, but it would be easy to override this for data that needs special treatment. Just write a new data holding program that implements the special treatment you want and knows how to register with the standard directory processes. [1] https://news.ycombinator.com/item?id=8311532 https://news.ycombinator.com/item?id=8311532
- pmontra 6y ago> If you have some data that you want to keep, you have a process that holds it in its process memory, and can give it other process via an IPC mechanism. Basically this is how Erlang / Elixir programs store state. Look for Elixir's GenServer behavior.
- kimi 6y agoYou should definitely look into Erlang then.
- webmaven 6y ago
- fl0wenol 6y agoThis is basically how the Palm Pilot worked. The RAM in the system was a developer-invisible cache that sat on top of a record-oriented access layer on top of the nonvolatile flash and system ROM. I'm simplifying slightly but it's the same idea. It worked okay but had its quirks.
- mongol 6y agoDid not also Newton have something of that kind?
- protomyth 6y agoThe Newton did have a storage called Soups. It was extremely fun to program and I miss it dearly.
- andrewshadura 6y agoIn fact, Palm Pilot didn't have proper non-volatile memory, instead, it had static RAM, which would preserve data for some time even if you swapped the batteries.
- lproven 6y ago[Author of the piece here] Yes, indeed - I specifically discussed that in the talk. The Palm platform sold over 50 million units, with no filesystem at all. This shows the tech is valid for end-user devices, IMHO.
- Animats 6y agoIt's not that new an idea. Keeping everything in persistent memory has been tried quite a few times. LISP went down that road, with Interlisp and Symbolics. Everything is in one persistent LISP image, and you save entire images if desired. Symbolics had some extra hardware support to tag objects in memory and get some level of pointer safety. OS/400, and to a lesser extent the B5500 and successor machines, went down that road too. That model was "everything is a relational database." OS/400 had a 20 year run; released in 2008, end of life in 2018. Other ideas that never really caught on include hardware key/value stores, or "Smart RAM". That may come back, since accessing non-volatile RAM through disk drivers is inefficient. The talk seems mostly focused on GUIs, which is a separate issue. If you want to think about a new generation of operating systems, think about what to do in the GPU space. That's the future of hardware. Single CPUs have hit the wall on speed, but there's plenty of room for GPUs with more functional units. GPU programs are almost stateless. Very functional. But at some level you need state. How should that interact with a near-stateless GPU? Big unsolved problem.
- djrogers 6y ago> OS/400 had a 20 year run; released in 2008, end of life in 2018 Err, setting aside the math inconsistency there, AS/400 was released in 1988, and the 2 most recent versions are still supported.. [0] https://www.ibm.com/support/pages/release-life-cycle https://www.ibm.com/support/pages/release-life-cycle
- chubot 6y agoDoesn't iOS have some kind of persistent memory abstraction? It seems more like a single level to me. Safari on iOS saves tons of tab state going back months, but it's not using all your memory, etc. I have never really done iOS programming so I don't know the details.
- astrange 6y agoThat’s called restorable state and it’s better than assuming everything can be always persistent, like Lisp/Smalltalk images did. For one thing, restarting all the time makes it less fragile. You don’t have to untangle your state that’s been persistent for months if there’s a bug in it.
- zepatrik 6y agoI also don't quite get why you would ditch files/directories which are just a way of organizing data. You still have to organize them if everything is in main memory. Also, sharing data between programs has to be possible somehow. You will need some kind of reference/pointer to the data you talk about. Why are directories, files, and paths such a bad idea for that?
- scroot 6y agoTo take the Smalltalk angle on this, instead of files you simply have everything in the system described as live objects. These are different from files because they are not just data. A system comprised of such objects has no "applications" or "programs" in the conventional sense -- you just have certain arrangements of objects interacting with each other. This is much more flexible, dynamic, and explorable than just having files for data and stovepiped programs that read those files.
- astrange 6y agoApps would still appear in a system like this as soon as you have third-party developers, as a natural consequence of Conway’s law. And once you have that, there’s also security and principles like the rule of least power that motivate the current design which you haven’t gotten rid of.
- samatman 6y agoAs a matter of user experience, rather than implementation, the 'filesystem' in iOS is just an app. It's one way to handle data sharing and transfer between apps, but it isn't always the best, nor is it the main one. This has some tradeoffs, everything does, but I'm glad someone is exploring the OS space without considering filesystems as we currently understand them to be an inevitable part of that. I can imagine an object capabilities framework, in which a 'filesystem' is just an object which owns data, organizes it in the familiar way, and shares capabilities with other objects, being quite useful and powerful.
- gcblkjaidfj 6y agodecades ago i was following a kid's graduation project of a OS with full permanence design. that was before Android and other always on "computers". it was called something like unununium (yeah, same name as the element, for extra hard-to-search points). I noticed the project when he suggested unununium-time as an alternative to linux time in a list was at, to fix some time skew problems... But what caught my interest was his vision that in the near future (remember, before android/IOS) computers would not care about offline data storage and a OS should be optimized for always-on and RAM only. I can still find some of the assembly versions, but the fun stuff and interesting ideas showed up on a rewrite in python(!) and that i can't find anything any more. edit: here's the best i could find https://web.archive.org/web/20060208191407/http://en.wikipedia.org:80/wiki/Unununium_%28operating_system%29 https://web.archive.org/web/20060208191407/http://en.wikiped... seems the vision was to threat the persistent storage as the only system memory.
- BlueTemplar 6y agoNVRAM then?
- gcblkjaidfj 6y agothe visionary aspect was that it didn't need new hardware concepts. Just drop the ephemeral ram (or treat it like L4 cache, so to say) and hope permanent storage gets faster, which it did.
- deleted 6y ago[deleted]
- justizin 6y agoI think this is really interesting, but I don't see any reason why you'd abandon the idea of a filesystem. UNIX has been consistently useful for all sorts of purposes largely because of the everything-is-a-file concept. Are we going to keep only a single copy of everything in memresister or whatever? someone will reinvent raid, and someone will reinvent the disk controller. i'm sure this tech will change all kinds of things but why wouldn't i want a simple hierarchial naming system to refer to all of the different blobs i have? that said, i'm sure i'll watch this!
- klodolph 6y agoThe filesystem, at least the Unix concept of it, is nice in theory but surprisingly ill-suited for anything besides, say, batch processing, once you start to look more closely at it. If you look at projects like SQLite or PostgreSQL, you’ll see all the fantastic, precise logic you need in order to ensure expected levels of consistency when you are using real filesystems to store data in a database. These problems come with serious enough pitfalls and traps that it’s common to see blanket recommendations to avoid directly interacting with the filesystem altogether, and simply do everything through SQLite or another library when possible. At the other end, if you look at GUI applications, the filesystem is a bit lower-level than it should be. At least, the Unix concept of filesystem is too low-level. If I open a file in a word processor, save it, shouldn’t I be able to move around the file and rename it in the file browser, without affecting the relationship of that file to the word processor? This is possible on a Mac, but this is done with APIs inherited from the pre-Unix days of macOS.
- johnvaluk 6y agoA file is more than simply a unit or collection of data in a local hierarchy. It's an abstraction that supports the copying, exchange and even possession of data. How is one supposed to share part of a database with another system or user without ultimately resorting to the file metaphor?
- klodolph 6y ago> How is one supposed to share part of a database with another system or user without ultimately resorting to the file metaphor? It is exceptionally difficult to share a database using files. This is probably one of the worst ways to share a database. Most of the time, the best you can do is take a snapshot of the database, dump it to a file, and import it into another system. Generally you would want to share a database by granting multiple users access to a single running instance.
- austincheney 6y agoThe author is conflating hardware and logic. A hard drive is hardware but a file system is a logical tree. The author provided simplistic reasoning for abandoning a type of hardware but no reasoning for abandoning file systems. If not a file system then what? Don’t say RAM, because that is still hardware.
- sthnblllII 6y agoYea, a hierarchical system for organizing data seems useful even if its stored on the same physical medium as main memory. Your profile is Highly Appropriate btw.
- tadfisher 6y agoIt is useful but limiting. The point of the logical tree is to index files, but a tree is a subset of more powerful indexing methods. Relational and graph structures come to mind. Incidentally, databases exist to marshal indexed data so that it's not visible or managed by the file system. This seems like something a non-hierarchical file system would supplant, which would allow for interoperability with file-oriented tools.
- astrange 6y agoThe problem with starting over is that you don’t understand how the current state came to be, so you’ll probably just reinvent it instead of getting anywhere new. See Chesterton’s fence.
- lproven 6y ago[Author of the piece here] I suggest reading the script. https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VRJ8OxpVdkzHxQF_8X5So/edit?usp=sharing https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VR... There is a lot of history in it, and that is entirely intentional.
- jecel 6y agoSince I design processors for Smalltalk I am certainly in favor of the ideas you present. I think the main thing that kept Plan 9 from becoming popular was that AT&T tried to make money on it at a time when Linux was already a big thing. By the time they gave up and open sourced it several of its unique features had been included in Linux. Squeak is not implemented in C but in a restricted subset of Smalltalk (called Slang) which can be easily translated to C. But since it is Smalltalk it can be tested using Squeak's nice development tools instead of gdb or similar. Although Lisp machines were more commercially successful, there were many interesting Smalltalk machine projects as I pointed out in these slides: http://www.merlintec.com/download/2019_slides_jecel_fast1v2.pdf http://www.merlintec.com/download/2019_slides_jecel_fast1v2....
- GekkePrutser 6y agoIntel actually discontinued Optane for consumers so this won't really fly... At least not yet. I do think a completely out-of-the-box rethink of computing could lead to very interesting results though!
- lproven 6y ago[Author of the piece here] No, they did not. They discontinued the SSDs. The NVDIMMs are not affected.
- GekkePrutser 6y agoBut they were never a consumer product in the first place :) Not saying that they couldn't be useful to consumers, but they're not sold for consumer hardware like intel. They have some strange preconceptions about what consumers need, unfortunately. The same way we still don't have ECC memory in 2021 :/
- lproven 6y agoOK, yes, fair points. :-) I discovered something that I didn't know in the Q&A afterwards: that flash SSDs can be permanently damaged if the power goes out unexpectedly. https://www.atpinc.com/blog/how-industrial-SSDs-handles-power-loss https://www.atpinc.com/blog/how-industrial-SSDs-handles-powe... Optane fixed this, or rather, was not affected. This is not such a bad issue in laptops, but it's a potential killer in desktops with SSDs. Perhaps if Intel had marketed Optane SSDs better, they'd have sold to enthusiasts for just this reason...
- GekkePrutser 6y agoTrue, I was definitely interested myself. Not really for this reason (my important stuff is triple-backed-up including offsite :) ) but for the great performance. But I was waiting for the price to drop a bit. It didn't really happen. I totally agree, Intel is very poor at marketing.
- moonbug 6y agoparahrqph five before mentioning lisp and Psion. pretty restrained for Liam!
- lproven 6y agoAhahaha! OK, it's a fair cop, but the industry's to blame. :-D
- dshpala 6y agoSurprised no one mentioned https://en.wikipedia.org/wiki/Phantom_OS https://en.wikipedia.org/wiki/Phantom_OS
- avmich 6y agoLooks to me like an outdated idea, at least on the concept level :) . Had similar thoughts around 2002, the closest thing to it was Ousterhout's RAMCloud. Today an approach would be to look at merging CPU and RAM.
- ARandomerDude 6y agoI'm not a kernel dev, or anything remotely close to it, but it seems to me that purely nonvolatile memory would have the unhappy side effect of not being able to just reboot the machine when things aren't running quite right. It's amazing how often this fixes problems, even in 2021.
- deleted 6y ago[deleted]
- lproven 6y ago[Author of the piece here] I did actually consider this. When your memory contents are persistent, there is no "boot process". Booting means loading OS code from secondary storage into RAM and then executing it. If there's no secondary storage, this is never normally needed. However, there is absolutely no reason why you cannot _re-initialise_ the system. Start again at first run, reset temporary data and run it from scratch. Secondarily, you could of course dump your data and work in progress to (say) a reserved memory partition first, or over the network to a remote server. Then you re-start and choose what you want to reload.
- ir193 6y agoThere're so many screenshots of GUIs. But there is a heavy path dependence on customer-facing GUI systems. A starting over on OS seems more likely to happen on cloud OS. In any case, the question is do we really need the existing OS abstractions if we implement everything in managed languages? [1] https://www.microsoft.com/en-us/research/publication/singularity-rethinking-the-software-stack/ https://www.microsoft.com/en-us/research/publication/singula...
- lproven 6y ago[Author of the piece here] Ignore the slides. The slides are decoration. Read the script, or listen to the talk. https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VRJ8OxpVdkzHxQF_8X5So/edit?usp=sharing https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VR...
- jacknews 6y agoIsn't this just a SASOS? https://en.wikipedia.org/wiki/Single_address_space_operating_system https://en.wikipedia.org/wiki/Single_address_space_operating...
- zelon88 6y agoI don't see what's so groundbreaking here. It looks like a lot of back patting. You've basically described a classical von Neumann architecture. The only reason hard drives were added to that is because volatile memory is expensive and the only reason why we don't use flash memory instead is because flash is not performant enough. The proposal has never been impossible. Just impractical and non performant in the real world. There's no such thing as "terabytes of non volatile memory" without either spending hundreds of thousands of dollars on RAM or settling for slow flash RAM.
- lproven 6y ago[Author of the piece here] Back patting? Whose? This is entirely orthogonal to stuff like von Neumann architectures. The core change is eliminating the distinction between primary and secondary or auxiliary storage: https://en.wikipedia.org/wiki/Computer_data_storage#Secondary_storage https://en.wikipedia.org/wiki/Computer_data_storage#Secondar... > There's no such thing as "terabytes of non volatile memory" without either spending hundreds of thousands of dollars on RAM or settling for slow flash RAM. You are technologically out of date. This is commercial, shipping technology now. https://www.storagereview.com/news/intel-optane-dc-persistent-memory-module-pmm https://www.storagereview.com/news/intel-optane-dc-persisten...
- ksec 6y agoI love people experimenting with new OS paradigm. Although I was expecting something else. But getting 8GB of Super Fast Memory + SSD will forever be cheaper than persistent memory. Not to mention persistent memory is nowhere as fast as DRAM. There are far more benefits with CPU and GPU sitting next to each other sharing the same memory address space, this requires high bandwidth memory. Which basically means there is no cost incentive unless this shift provides some gigantic leap forward in value.
- lproven 6y ago[Author of the piece here] This is technologically out of date, I'm afraid. You appear not to have read about Intel 3D Xpoint and related tech. https://en.wikipedia.org/wiki/3D_XPoint3 https://en.wikipedia.org/wiki/3D_XPoint3 This is retail tech now, under the brand name Optane: https://www.storagereview.com/news/intel-optane-dc-persistent-memory-module-pmm https://www.storagereview.com/news/intel-optane-dc-persisten... SSD is cheaper than RAM. Optane is orders of magnitude cheaper, faster and longer-lived than SSD. It is here now. The value is discussed in the talk; I suggest reading the script. https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VRJ8OxpVdkzHxQF_8X5So/edit?usp=sharing https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VR...
- ksec 6y agoI am aware of Optane. But even in its current best, 2nd Generation Optane Memory DIMM and not the the Optane SSD, both its Latency and Bandwidth doesn't come close to DRAM. Even IBM innovation of OMI ( Open Memory Interface ), allowing Petabyte of Memory while only adding 10ns of latency to DRAM were already met with some scepticism. And Optane DIMM is at least adding 50ns at best, and hundreds at worst. Our Multi-Core CPU, and the roadmap of SoC, merging CPU, GPU and VPU are already meet with some Memory Bandwidth bottleneck. Intel has also stopped all consumer / retail of Optane. They will only be available on server and probably from selected partner from now on. Optane is cheaper than DRAM per GB, but it isn't cheaper than NAND SSD unless you take into account of TCO. Which I would argue is still more expensive than SSD given the cost of SSD has declined quite a bit ( or back to normal depending on how you look at it ). But Optane ( both DIMM and SSD ) is faster than SSD especially in IOP heavy operation so it is still worth the money depending on applications. Lastly, no one has a clear roadmap on Optane or 3D XPoint cost reduction. There is a difference of we want to reduce our cost and we know how to reduce our cost. 3D XPoint's Fab has been under utilize from Day one and are currently making a small loss even with Intel's guarantee purchase agreement. ( And Intel aren't selling all of them either ) There are nothing in the next 3 years that changes this landscape, and considering how technology moves, I would bet that 5 years down the line things would be about the same. I dont want to be too dismissive. I would surely want Persistent Memory and a computer that just turned on like the old days with a press of power button. And the revival of SmallTalk like OS! But right now It doesn't seem feasible in the foreseeable future without some massive trade offs.