From: Vladimir Sedach <vas@oneofus.la>
To: Wayne <waynedpj@ingiro.xyz>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Shepherd and Guille
Date: Thu, 08 Nov 2018 21:18:06 -0800 [thread overview]
Message-ID: <4724.53352199427$1541740617@news.gmane.org> (raw)
In-Reply-To: <20181107231234.Horde.GJcOfWxRUgR6leHv2K2Odev@mail.ingiro.xyz>
> thank you both Vladimir and Pierre for taking the time to respond.
> while i also thought that the article was not so well done, the point
> about using GC/JIT/etc. languages for "critical" software like init
> seemed somewhat worth investigating. thus thanks again for your
> inputs.
Sorry, I should have given more details when mentioning BBN Lisp.
These investigations have already been done in the 1970s.
There were several operating systems built at Xerox PARC, in
Smalltalk and in INTERLISP, for various kinds of hardware (including
PCs with Intel microprocessors¹). There was the ZetaLisp based series
of operating system originating out of MIT. Takashi Chikayama²
implemented micro-controller Lisp systems on Intel processors starting
in 1976.³
Since that work in the 1970s, the only unsolved problem for using
dynamic languages in systems programming has been designing a hard
real-time garbage collector, and that has been solved in 2003 at
IBM.⁴
¹ https://oneofus.la/have-emacs-will-hack/2012-01-11-the-personal-computer-you-havent-heard-of.html
² http://www.logos.ic.i.u-tokyo.ac.jp/~chik/
³ http://www.softwarepreservation.org/projects/LISP/utilisp/utilisp/IPSJ-JIP1303003.pdf
⁴ https://researcher.watson.ibm.com/researcher/files/us-bacon/Bacon03Metronome.pdf
next prev parent reply other threads:[~2018-11-09 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 0:39 Shepherd and Guille Wayne
2018-11-01 4:19 ` Vladimir Sedach
[not found] ` <87o9b9ig4l.fsf@exinda.orion.oneofus.la>
2018-11-04 9:39 ` Pierre Neidhardt
2018-11-08 4:12 ` Wayne
2018-11-08 7:58 ` Pierre Neidhardt
2018-11-09 5:18 ` Vladimir Sedach [this message]
[not found] ` <5be518c9.1c69fb81.90d67.495dSMTPIN_ADDED_BROKEN@mx.google.com>
2018-11-10 1:46 ` Maxim Cournoyer
2018-11-13 4:22 ` Wayne
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='4724.53352199427$1541740617@news.gmane.org' \
--to=vas@oneofus.la \
--cc=help-guix@gnu.org \
--cc=waynedpj@ingiro.xyz \
/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).