From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Gecko based web browser
Date: Wed, 19 Jul 2000 09:43:38 +0200 [thread overview]
Message-ID: <20000719094337.B3081@cackle.proxima.alt.za> (raw)
In-Reply-To: <200007190718.DAA24199@cse.psu.edu>; from forsyth@caldo.demon.co.uk on Wed, Jul 19, 2000 at 08:18:36AM +0000
On Wed, Jul 19, 2000 at 08:18:36AM +0000, forsyth@caldo.demon.co.uk wrote:
> it seems a bit pointless to implement the transport without being
> able to replay the sounds it contains.
Not altogether, one may want to record it, or perhaps we can figure a
way to pipe to a win box, if there's no other option. Consider that
squid is not entirely superfluous :-)
I think we should look at a browser that has the facilities for
plug-ins, make the latter as simple as possible and let history takes
its course.
I think it was Diamond that eventually regretted their decision not to
disclose to the XFree86 boffs how their VGA adapters operated.
And, I hasten to add, if we have the infrastructure in place, we can
easily ride the wave of supply meeting demand (consider CSS as a case
in point) currently being driven by the Linux community. But we do
need to build the foundations for it (and a little more, when it comes
to web browsers and, I'd like to repeat, graphic rendering engines).
++L
PS: I think this forum has been wonderful in one particular respect,
namely in discouraging kitchen-sinkenitis, with sensible reasoning.
I'd like to see more ideas being proposed here, and the same careful
consideration given to them. There are many neophytes that, not
unlike me, still do not altogether grasp the philosophy behind Plan 9
and I believe it does not hurt to emphasise it by example on a regular
basis. There are also many capable developers that only need some
encouragement to take Plan 9 further.
next prev parent reply other threads:[~2000-07-19 7:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 7:18 forsyth
2000-07-19 7:43 ` Lucio De Re [this message]
2000-07-19 7:58 ` Randolph Fritz
2000-07-19 15:23 ` Jonathan Sergent
-- strict thread matches above, loose matches on Subject: below --
2000-07-26 17:43 miller
2000-07-26 17:50 ` James G. Stallings II
2000-07-27 7:43 ` Matt
2000-07-27 7:54 ` Lucio De Re
2000-07-27 17:28 ` Matt
2000-07-20 4:05 James A. Robinson
2000-07-20 1:41 rob pike
2000-07-20 8:34 ` George Coulouris
2000-07-18 23:02 forsyth
2000-07-18 22:30 ` Frank Gleason
2000-07-19 0:17 ` Randolph Fritz
2000-07-19 0:01 ` Frank Gleason
2000-07-19 1:02 ` Skip Tavakkolian
2000-07-19 11:45 ` Theo Honohan
2000-07-18 22:33 rob pike
2000-07-18 22:59 ` Howard Trickey
2000-07-21 8:34 ` Alt
2000-07-25 15:07 ` Douglas A. Gwyn
2000-07-18 20:23 miller
2000-07-18 22:07 ` Randolph Fritz
2000-07-18 19:03 Stephen Harris
2000-07-18 19:17 ` Andrey Mirtchovski
2000-07-18 23:48 ` Randolph Fritz
2000-07-19 5:40 ` Randolph Fritz
2000-07-19 9:26 ` Michael Dingler
2000-07-19 15:22 ` Douglas A. Gwyn
2000-07-19 16:28 ` Andrey Mirtchovski
2000-07-19 16:47 ` Randolph Fritz
2000-07-19 22:52 ` sah
2000-07-20 1:16 ` James A. Robinson
2000-07-20 3:08 ` Boyd Roberts
2000-07-26 8:42 ` Ralph Corderoy
2000-07-19 9:27 ` Christopher Browne
2000-07-19 15:24 ` Andy Newman
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=20000719094337.B3081@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).