The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Ron Natalie" <ron@ronnatalie.com>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: OLIT, MoOLIT, and NeWS (was: X11 Conservancy Project)
Date: Sun, 25 Dec 2022 21:47:20 +0000	[thread overview]
Message-ID: <em15185aa0-372c-4874-95c9-a0b803f2154a@9a0c19f5.com> (raw)
In-Reply-To: <CAFZukdTGRJqmJhtXmKtuoK3XuHm9sTgSE4_ooBF2p=fLw5u10g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]

Much as I was a fan of NeWS back in the day (and later used a NeWS-ish 
complete with the Owen Densmore object oriented extensions) postscript 
interpreter as the basis for our product,
I’m having some issues with that “history.”   First off, you couldn’t 
arbitrarily cat a PostScript file to the screen and expect it to work.   
There were enough differences between Adobe and the NeWS version to 
cause problems.

The idea of putting small programs (written in PostScript) to handle the 
interaction was an interesting one.   The problem is that writing stuff 
in PostScript (even with the NeWS extensions) is so godawful that I have 
my doubts about having implemented an entire X Server in one (having 
written several X Servers subsequent to that).

Of course, Gosling came up with a more palatable development language 
for the next attempt:   Java.


------ Original Message ------
From "josh" <joshnatis0@gmail.com>
To "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc "tuhs@tuhs.org" <tuhs@tuhs.org>
Date 12/25/2022 4:38:32 PM
Subject [TUHS] Re: OLIT, MoOLIT, and NeWS (was: X11 Conservancy Project)

>>Ranging a bit farther afield, I wonder similarly about Sun's NeWS, 
>>which
>>I never saw in the flesh.
>
>Branden,
>
>You may find this fellow’s archaeological dig on NeWS and PostScript 
>interesting: https://twitter.com/rsnous/status/788053163857379328
>
>He also attempted to make a NeWS clone: 
>http://dev.rsnous.com/dewdrop/executive/ (source available).
>
>Josh
>

[-- Attachment #2: Type: text/html, Size: 3214 bytes --]

  reply	other threads:[~2022-12-25 21:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 18:15 [TUHS] X11 Conservancy Project Michelangelo De Simone
2022-12-25 19:16 ` [TUHS] " segaloco via TUHS
2022-12-25 19:57   ` Michael Kjörling
2022-12-25 20:51 ` [TUHS] OLIT, MoOLIT, and NeWS (was: X11 Conservancy Project) G. Branden Robinson
2022-12-25 21:03   ` [TUHS] " Brad Spencer
2022-12-25 21:38   ` josh
2022-12-25 21:47     ` Ron Natalie [this message]
2022-12-26  6:26     ` arnold
2022-12-26 19:37       ` Jon Steinhart
2022-12-26  4:18   ` Warner Losh
2022-12-26  9:59 ` [TUHS] Re: X11 Conservancy Project Lars Brinkhoff

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=em15185aa0-372c-4874-95c9-a0b803f2154a@9a0c19f5.com \
    --to=ron@ronnatalie.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).