From: "Ron Natalie" <ron@ronnatalie.com>
To: "Rich Morin" <rdm@cfcl.com>,
"Tautological Eunuch Horticultural Scythians" <tuhs@tuhs.org>
Subject: [TUHS] Re: FYI: Apple Lisa [source Pascal code] goes “open source”
Date: Fri, 20 Jan 2023 17:07:17 +0000 [thread overview]
Message-ID: <eme23c9bd0-8815-4147-8237-61be2f5000ba@e41218a5.com> (raw)
In-Reply-To: <B78462CC-1C58-4A20-8753-351E1923495B@cfcl.com>
Nothing about the LISA OS or the subsequent MAC XL (extra large? extra
Lisas in inventory?) is remotely UNIXy.
------ Original Message ------
From "Rich Morin" <rdm@cfcl.com>
To "Tautological Eunuch Horticultural Scythians" <tuhs@tuhs.org>
Date 1/20/2023 11:54:07 AM
Subject [TUHS] FYI: Apple Lisa [source Pascal code] goes “open source”
>Pioneering Apple Lisa goes “open source” thanks to Computer History Museum
>Lisa OS 3.1's 1984 source Pascal code now available under a non-commercial license.
>https://arstechnica.com/information-technology/2023/01/pioneering-apple-lisa-goes-open-source-thanks-to-computer-history-museum/
>
>CHM MAKES APPLE LISA SOURCE CODE AVAILABLE TO THE PUBLIC AS A PART OF ITS ART OF CODE SERIES
>https://computerhistory.org/press-releases/chm-makes-apple-lisa-source-code-available-to-the-public-as-a-part-of-its-art-of-code-series/
>
>-r
>
next prev parent reply other threads:[~2023-01-20 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:50 [TUHS] Managers/architects (was: AIX moved into maintainance mode) Noel Chiappa
2023-01-19 18:00 ` [TUHS] " Marc Donner
2023-01-19 18:09 ` Charles H Sauer (he/him)
2023-01-20 3:47 ` John Cowan
2023-01-20 16:54 ` [TUHS] FYI: Apple Lisa [source Pascal code] goes “open source” Rich Morin
2023-01-20 17:07 ` Ron Natalie [this message]
2023-01-19 21:12 ` [TUHS] Re: Managers/architects (was: AIX moved into maintainance mode) Lawrence Stewart
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eme23c9bd0-8815-4147-8237-61be2f5000ba@e41218a5.com \
--to=ron@ronnatalie.com \
--cc=rdm@cfcl.com \
--cc=tuhs@tuhs.org \
/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 NNTP newsgroup(s).