News for hackers. Stuff that matters.
Re:Tmpfs considered harmful by prodigal_erik on Wednesday September 12, 2012 @12:22PM (#4511407)
RAM really is a harmful kludge. Neither Turing machines nor lambda calculus call for some of an algorithm's state to suddenly be obliterated. The only reason we put up with it is that disk and SSD are so much slower.
Re:Tmpfs considered harmful by rwallace on Wednesday September 12, 2012 @03:09PM (#4512469)
Speed is not the only benefit of RAM. The internal data structures of most programs are gnarly messes of intertwined pointers, fragile, easily corrupted, hard to upgrade in place, almost impossible to fix when they break. The division between RAM and disk forces everything to be serialized at intervals to clean storage formats that can be reread for a fresh start. As a practical matter, that's a big enough benefit to justify enforcing the division at an API level even if disk were as fast as RAM.
Re:Tmpfs considered harmful by prodigal_erik on Thursday September 13, 2012 @12:43PM (#4517153)
The industry might produce less worthless crap without the crutch of "it's not quite unusable if you start over often enough".
Re:Tmpfs considered harmful by TylerE on Wednesday September 12, 2012 @05:52PM (#4513445)
I've never understood the obsession with Turing machines. It's like basing one's core belief of what a car is off one of Da Vinci's crazy wind-up things.
Re:Tmpfs considered harmful by cma on Wednesday September 12, 2012 @09:09PM (#4514227)
Ram is just state. Turing machines require a non-tape state machine mechanism. You could consider ram a part of that, 4 gigs corresponding to many many possible states.
Re:Tmpfs considered harmful by saurik on Thursday September 13, 2012 @01:32AM (#4514919)
Some people (I do not agree with this view) believe that applications should be universally persistent: so that they never "stop running" and never "lose data" even when the machine restarts or even if the programs are transferred between systems.