From: kjn9@citizenearth.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9x and similar old apps
Date: Sat, 16 Nov 2002 10:52:19 -0500 [thread overview]
Message-ID: <20021116155054.25738.qmail@mail.dirac.net> (raw)
kjn9@citizenearth.com>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.11
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
Date: 16 Nov 2002 15:50:54 -0000
There's a lot of stuff that is either documented, or is rumoured to have existed, but is not in the 4th Edition, probably for sound reasons:
alef
C++ compiler
X server
panel library (graphics)
native port of limbo's Tk library (was this the same thing as the panel library?)
native port of charon web browser
Some of these would help attract a bigger community, by allowing a larger range of applications to be ported to Plan 9. The most useful in this regard would of course be the X server - but perhaps X11 is too large to port from the 2nd edition and to maintain (as well as not doing things the "Plan9 way").
Tk is a small widget library that would be very useful, because it is still the most popular widget set for perl, python, and tcl. This would give us access to a huge number of graphical scripts (and an incentive to port tcl), and reduce the Plan 9 learning curve for a large number of Unix developers.
next reply other threads:[~2002-11-16 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 15:52 kjn9 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-16 16:52 Russ Cox
2002-11-15 16:48 a
2002-11-15 2:40 Russ Cox
2002-11-15 5:18 ` Dan Cross
2002-11-15 2:14 Russ Cox
2002-11-15 1:58 Joel Salomon
2002-11-15 2:30 ` andrey mirtchovski
2002-11-15 1:46 Russ Cox
2002-11-15 1:41 Joel Salomon
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=20021116155054.25738.qmail@mail.dirac.net \
--to=kjn9@citizenearth.com \
--cc=9fans@cse.psu.edu \
/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).