From: Grant Rettke <gcr@wisdomandwonder.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: Emacs Help <help-gnu-emacs@gnu.org>
Subject: Re: [FYI] The Lisp Machine is back
Date: Sat, 20 Sep 2014 20:18:38 -0500 [thread overview]
Message-ID: <CAAjq1mem+3fBeWgxSpj3obL3AfFAgh27XPxzhJQcZYfvoOPUTQ@mail.gmail.com> (raw)
In-Reply-To: <87d2ara5nv.fsf@gmail.com>
Wonderful!
Grant Rettke
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
On Fri, Sep 19, 2014 at 12:20 PM, Thorsten Jolitz <tjolitz@gmail.com> wrote:
>
> Hi List,
>
> Emacs success as an editor or rather an OS is sometimes explained by
> its (at least superficial) similaritiy to a LispMachine [fn:1]:
>
> ,----
> | Emacs as a LispMachine
> |
> | Some people have started to refer to Emacs as a LispMachine. It is
> | not strictly a LispMachine because, clearly, it is a software
> | program and not a physical computer, but as that line starts to blur
> | it seems like a useful epithet for Emacs because these days Emacs
> | look more and more like an operating system.
> `----
>
> Today a modern 64bit LispMachine, based on one of the most exciting Lisp
> dialects around, has been announced [fn:2]:
>
> ,----
> | PilMCU is an implementation of 64-bit PicoLisp directly in hardware. A
> | truly minimalistic system. PicoLisp is both the machine language and the
> | operating system:
> |
> | * Memory management is trivial, just the Lisp heap and the stack
> | * The built-in database is extended to hold a "file system"
> | * One SSD per database file for mass storage
> | * "Processes" run as tasks and coroutines
> | * Events (timing and interrupts) via a 'wait' instruction
> | * Complex I/O protocols are delegated to peripheral chips
> |
> | The final hardware can be very lightweight. Low transistor count and
> | power consumption. No overhead for an OS. It is conceivable for a later
> | stage to put many interconnected CPUs on a single chip.
> |
> | At present, we have it running in the Verilog simulator, and in an
> | emulator (adaption of the PicoLisp 'emu' architecture). [...]
> |
> | We imagine something in the line of an "Embedded Lisp Machine" or a
> | "Lisp Machine Kit". Perhaps for home brewing, educational institutions
> | and/or robotics research?
> `----
>
> I thought this might be interesting for Emacs hackers and user too.
>
> * Footnotes
>
> [fn:1] http://www.emacswiki.org/emacs/LispMachine
>
> [fn:2] http://www.mail-archive.com/picolisp@software-lab.de/msg04823.html
>
>
> --
> cheers,
> Thorsten
>
>
next prev parent reply other threads:[~2014-09-21 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 17:20 [FYI] The Lisp Machine is back Thorsten Jolitz
2014-09-21 1:18 ` Grant Rettke [this message]
[not found] ` <mailman.9281.1411262328.1147.help-gnu-emacs@gnu.org>
2014-09-21 1:55 ` Emanuel Berg
2014-09-21 2:41 ` Chris F.A. Johnson
[not found] ` <mailman.9284.1411267342.1147.help-gnu-emacs@gnu.org>
2014-09-21 3:11 ` Emanuel Berg
2014-09-21 3:17 ` Emanuel Berg
2014-09-21 13:28 ` Grant Rettke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAjq1mem+3fBeWgxSpj3obL3AfFAgh27XPxzhJQcZYfvoOPUTQ@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tjolitz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).