keeping data in memory not disk

keeping data in memory not disk





gavino
View profile
More options Jun 22, 4:51 am
Newsgroups: comp.lang.forth
From: gavino
Date: Tue, 22 Jun 2010 04:51:48 -0700 (PDT)
Local: Tues, Jun 22 2010 4:51 am
Subject: keeping data in memory not disk
Reply | Reply to author | Forward | Print | Individual message | Show original | Remove | Report this message | Find messages by this author
I notice mr moore and paul graham talk about keeping things in memory.

avoiding disk

then things are very fast

what about dangers of power failure etc?

it does seem very powerful to keep it all in ram

http://colorforth.com/cf.htm
Rationale
Current software is shameful. Giant operating systems linger from the
1970's. Applications are team-produced with built-in obsolescence.
User interfaces feature puzzle-solving.
With the huge RAM of modern computers, an operating system is no
longer necessary, if it ever was.

http://paulgraham.com/vwfaq.html
How did the editor handle client sessions?

There was one Lisp process for each user. When someone logged in to
edit their site, we'd start up a new process and load all their data
into memory. From that point they had an ongoing conversation with
that process.

Because everything was already loaded into memory, we never had to
read anything from disk or start up a process to respond to an HTTP
request. All we had to do was evaluate a closure stored in memory.