3 ms·
What takes most time when suspending a laptop now, AFAICT, is powering down various I/O devices, and giving software some time to react to that. A system where
by nine_k 5y ago
What takes most time when suspending a laptop now, AFAICT, is powering down various I/O devices, and giving software some time to react to that.
A system where RAM is non-volatile can have great many computations running concurrently. No need to "start" a program, its running state just stays since the last time. You may need to sometimes restart a program from a known good state, if things go wrong.
Also, all the undo info (subject to space limits) is persisted and available whenever needed. All the auxiliary structures for a document / picture / code you work on just live next to them, are them. To send a document, you export it to an accepted format, detaching from the in-program representation.
- wizzwizz4 5y agoWe can have this architecture today. Writing an OS is hard, though.
- nine_k 5y agoHalfway, I'd say, because even if NVMe is fast, it's not that fast. For instance, an IDE, instead of keeping the parse trees in RAM, has to use a database on a disk for persistence, while caching a hot subset in RAM for speed. When all of your disk becomes RAM disk, only persistent, things already change in interesting ways. But hardware based on a persistent-RAM-only design would definitely need a very different OS. (With a Linux compatibility layer, inevitably, though.)
- spitfire 5y agoSo like a smalltalk or lisp based image system. I’m down for that.
- inetknght 5y ago> What takes most time when suspending a laptop now, AFAICT, is powering down various I/O devices, and giving software some time to react to that. tbqh that's a problem with software design. It's better to just power down devices and not let software react. That would force software to handle unexpected failures much more gracefully and we'd all be better for it.