tfw zen 5 is soon going to be released
there is a non-zero chance of me buying it
@iska threadripper 7000 series looks rad. I hope they release more of them, I'd probably wanna buy one in a couple of years.
@newt@stereophonic.space I just want the 57-bit paging so I won't have to worry about running out of virtual memory when I'll eventually put all of my storage into virtual memory 
@iska that's sooo dumb on so many levels lmao
@newt@stereophonic.space managing between RAM and disk is awkward and produces bloat 
And I'm not even the first one to come up with idea, pretty sure that's what virtual memory was meant for in the first place
@iska no, it wasn't.
Imagine your system crashes. What is the state of your storage then? Naaaah...
The closest thing to your idea that was actually put into use was a sort of Object-Oriented Database storage approach from z/OS. They employed 128-bit pointers within this address space for persistent objects and implemented a database-like interface (ORM). But on disk, it still had a filesystem with files and shit.
Imagine your system crashes. What is the state of your storage then? Naaaah...
The closest thing to your idea that was actually put into use was a sort of Object-Oriented Database storage approach from z/OS. They employed 128-bit pointers within this address space for persistent objects and implemented a database-like interface (ORM). But on disk, it still had a filesystem with files and shit.
no, it wasn't.
I know Xerox gave Alto virtual memory for transparent persistance and being able to fit smalltalk inside the early 70s computer.Imagine your system crashes. What is the state of your storage then? Naaaah...
If your transparency code is good, crashes won't do damage. Reliability is kind of the point of a persistent system.There's actually a bunch of OSes with a transparently persistent, single-level store. EROS and Aurora come to mind.
Aurora actually improved RocksDBs performance while greatly shrinking the codebase.
@iska
>I know Xerox gave Alto virtual memory for transparent persistance and being able to fit smalltalk inside the early 70s computer.
Maybe, but that's Smalltalk-specific. Virtual memory was invented before that for different purposes.
>If your transparency code is good, crashes won't do damage. Reliability is kind of the point of a persistent system.
Is it ever good? I get the idea behind transparent persistency, but it isn't a replacement for file-based storage.
>I know Xerox gave Alto virtual memory for transparent persistance and being able to fit smalltalk inside the early 70s computer.
Maybe, but that's Smalltalk-specific. Virtual memory was invented before that for different purposes.
>If your transparency code is good, crashes won't do damage. Reliability is kind of the point of a persistent system.
Is it ever good? I get the idea behind transparent persistency, but it isn't a replacement for file-based storage.
but it isn't a replacement for file-based storage.
why not? 
It's not like I can't create a filesystem inside of it
@iska for a huge plethora of reasons. Versioning being one, file-sharing being the other, and so on.
