6 ms·
It'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. Eve
by Animats 6y ago
It'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
- Animats 6y agoSorry, I meant 1988. My bad. Wikipedia has old info about versions and end of life.
- protomyth 6y agoThey are not only still supporting it, it is a current product under a new name (IBM i). We just bought at S924 last year running IBM i.
- ThinkBeat 6y agoOS/400 and AS/400 are some of most underrated and unknown machines. AS/400 (I only used it back in those days, I don't know enough about newer series). Would run for years with no attention given to them. I saw people stuff it in a closet and forgotten about it. Some did have the smarts to rotate backup tapes then they knew where it was. If the machine needed help it would "call" IBM and report it, and there would be a technician there to help it before the customer knew there was a problem. As with many things, I wish IBM would make it GPL, but the changes of that happening is very low. Also the programming languages is not familiar to many
- protomyth 6y agoThe current machines we have (S924) calls IBM by itself. It had a bad RAID card so an IBM technician showed up and replaced it. It is a bit strange as a System Admin being the second one called. We do a daily tape backup. LTO-7 is big enough to hold all the financial data. There is also a couple of companies that will do automatic offsite backup for a very reasonable price. They will even stage the data to a hosted environment until you can get a replacement machine (and I suppose a replacement building). I do wish IBM had a simulator or small machine that programmers could use. The cost of entry to write software for the things is way too high. I would like a BSD / MIT license as I am a BSD fan. Honestly, I wish I had time to work on a non-UNIX non-Windows Clone Operating System. Ideas like the AS/400 / IBM i architecture are amazing.
- hctaw 6y agoReal applications don't hit CPU walls, they're bottlenecked by I/O more often, and the biggest CPU wall is memory accesses. There is a lot of room for innovation there if you shirk off POSIX compatibility. Also, state is not a problem for functional semantics. Remember "functional" is a semantic distinction, it doesn't imply a ton about optimized implementations of those semantics. For a stateful system the only thing different about a functional approach is the programmer cannot express a program where yielding next state invalidates current state. Most of the time a sound, functional program can be compiled into in place (mutable) operations on the state, the difference is they're free of logical errors.
- ChuckMcM 6y agoYou are making the author's point for them :-). Now add in that some of the stuff that was "custom hardware" that supported the concept of 'always resident' OS state is now off the shelf (specifically Optane/Crosspoint stuff) Of course Intel killed of consumer Optane for SSDs so one wonders what is going on there. The second point, about how to think about GPUs in the context of "modern" computing is, for me, the more interesting one. As mobile processors have for years been a GPU with a processor accessory laptops and desktop computers seem to be headed that way as well. To be honest I'm surprised there isn't a GPU "motherboard that you can plug one or two CPU daughter cards into.
- juancampa 6y agoI wasn't aware that intel killed Optane-Only SSDs for consumers so I looked up and here's a recent article about it: https://www.tomshardware.com/news/intel-kills-off-all-optane-only-ssds-for-consumers-no-replacements-planned https://www.tomshardware.com/news/intel-kills-off-all-optane...
- Teknoman117 6y agoI think the answer as to why Optane consumer SSDs were killed off is fairly clear. They were 5 or 6 times the price per gigabyte as NAND based SSDs and didn't offer more performance in most consumer applications. The SOHO community didn't like them all that much either because the consumer Optane SSDs lacked most of the low queue depth performance that the enterprise disks are known for. Most consumers are also replacing their SSDs long before they actually wear out, so the extreme durability of Optane is kind of moot there. It's a fantastic enterprise product, but I don't think most consumers are really getting any extra value out of them over NAND at this point. The only guy I knew who bought one wanted to put their Gentoo build directory (/var/tmp/portage) on it.
- hinkley 6y agoI was stuck in the planning phase for a pet project up until a week ago, for a reason why Lisp and Smalltalk always made me nervous. Bugs can put your persistent state into uncharted territory, and there may be no clear path back. There's a reason we still have 'turn it off and back on again' in our bag of tools. Often it's the only thing that reliably works. This makes systems designed never to be shut down and turned back on again deeply unimpressive to the more practically minded members of the audience. One of the places persistent state crashes and burns is when the system of record and the source of truth combine. Once the source of truth breaks we can't know what's true anymore. My breakthrough was figuring out that I'm trying to get data from something that is already a pretty good system of record, I can just keep letting it do that job indefinitely. My source of authority needs to transform that data, not own it. As long as I can detect out-of-band changes to the system of record (which I can), I can always rebuild my models from scratch. That allows me some excellent test fixtures. That also gives me the option to do manual 'surgery' on the system of record rather than sinking my roadmap to implement a full feature to do something I might not need to do again for another year, or that no customer will ever see. I am just on the same continuum as everybody else. My code needs to make a lot of decisions. I can't afford to make them all from first principles every time. I need to store intermediate values. I also need to identify intermediate values and question them. If I don't get help with this from my architecture, myself and coworkers will blur the lines every time a problem seems a little beyond our abilities, and eventually nobody will know what's true anymore except the delusional ones. How do I know this? Because I have never seen any other outcome. The only differences are in how much surprise the team exhibits.
- klodolph 6y ago> There's a reason we still have 'turn it off and back on again' in our bag of tools. Often it's the only thing that reliably works. An alternative perspective—at the very large scale, the opposite may be true. Turning something off and then on again may be one of the worst ways to fix problems with certain large systems. At a large scale, you would document and manage the state of the system, make changes which put that system into a new state, and build tools that monitor and enforce system state (declaratively where possible, but it’s not always possible to be declarative). Sometimes there will be duplicated effort between making sure a system runs smoothly and making changes while it’s running, and making it so the system can turn off and on again. Think about the duplicated effort between setting up a new database and making schema changes to a live production database. YES, you want to have a source of truth. But the “turn it off and on again” source of truth is usually a sequence of imperative commands rather than a description of the desired system state, and comes with its own reliability problems. A description of system state as source of truth has a different set of reliability problems but I think it’s absolutely necessary to explore the solution space between these two extremes—shooting for a completely declarative system is futile, but an imperative system can be very hard to reason about.
- trasz 6y agoWait, OS/400 is going to be EOL-ed? How, why? :-/
- p_l 6y agoIt's not, bad source apparently misled commenter.
- Aerroon 6y ago>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. Will it be more like the web with HTTP?
- Aloha 6y agoOS/400 is very much alive, its called System i now.
- keithalewis 6y agoAs long as the problem you are trying to solve is shaped like rendering pixels on a screen, GPUs are great! The future is multicore processors not bottle necked by the bus to a GPU. And coroutines.
- megameter 6y agoI believe there are only two problems in computing: how data is divided up, and how data is bound together. They function nearly the same because you can use one to get the other, but the choice of which one to apply is critical and influences the shape of the media built on top. Where division is easy, things get shoved into countless categories. Where binding is easy, everything gets glued together. With respect to the issues of operating systems, "data" maps to "hardware resources". With execution logic, "data" maps to "software architecture". And so on.
- lproven 6y ago[Author of the piece here] Those are not things of central concern to me currently, but another project that has some similar central axioms is looking at just that. This talk is long but goes into quite a lot of depth. You might enjoy it. https://www.youtube.com/watch?v=bSNda9EzNOI https://www.youtube.com/watch?v=bSNda9EzNOI
- lproven 6y ago[Author of the piece here] Thanks for the comment. You do make me wonder if you listened to the whole talk, or read the script (https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VRJ8OxpVdkzHxQF_8X5So/edit?usp=sharing https://docs.google.com/document/d/1wM1-c7euvQaRaCL4hKCaE8VR...) I specifically addressed and discussed Lisp, Symbolics, & OS/400 (which is still alive and well). IBM i (as it's now called) seems to more or less treat everything as a single giant disk than as a single memory space, though. However, it's been hard to find solid info for non-IBM-specialists. It is not at all focussed on GUIs, no. However, I needed something pretty to put on the slides. The focus is explicitly, as discussed, on end-user general-purpose computers, not servers. Servers are very well-served (pun intended) already. Yes, I _know_ that this is not all-new. Indeed, that was one of my core points. The reasons are: [1] I think there is more significance to something obscure or niche that has survived for decades and is still actively maintained and used than almost any flashy new offering which could fizzle out again just as fast. [2] Using existing tech means that there are people out there with experience in it. It is not all-new for everyone. That's helpful. [3] I personally am not very interested in GPU tech, and I think the new Apple M1 ARM chips bear out why: the standalone super-powerful GPU with its own RAM is probably a temporary artifact of PC designs and the gaming market.