From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: Browsers (was: Re: Plan 9 annoyances (was: Re: [9fans] mv vs cp))
Date: Thu, 11 Oct 2001 12:41:20 +0100 [thread overview]
Message-ID: <20011011113820.6ED6919A61@mail.cse.psu.edu> (raw)
>>Perhaps someone in the Plan 9 world has implemented a `browser' for a
>>`web' document description language in Plan 9 style. There's no reason
>>why the Plan 9 form of innovation (step back, think, redesign and
>>rewrite) should not be applied to the Web, is there?
no, but i don't see wide-spread adoption as being particularly great,
so it's probably not worthwhile. it's one reason that W3C and XML mania worries me.
a proper pandora's box.
next reply other threads:[~2001-10-11 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 11:41 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 13:18 Plan 9 annoyances (was: Re: [9fans] mv vs cp) bwc
2001-10-10 8:57 ` Douglas A. Gwyn
2001-10-10 10:02 ` Browsers (was: Re: Plan 9 annoyances (was: Re: [9fans] mv vs cp)) Lucio De Re
2001-10-10 18:38 ` Steve Kilbane
2001-10-11 8:31 ` John Murdie
2001-10-11 17:26 ` Steve Kilbane
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=20011011113820.6ED6919A61@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).