9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mothra
Date: Wed, 19 Jul 2000 21:45:38 +0200	[thread overview]
Message-ID: <200007192045.VAA15726@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Wed, 19 Jul 2000 07:45:36 EDT." <006f01bff176$dab42fe0$62356887@HWTPC>

> You're kidding yourself if you think this comes anywhere near solving
> the big problems in writing a web browser.

I think we're looking at different problems.

To me, Plan 9 has always been about stepping back, looking at the
whole problem, and solving it with hindsight. Nods to the outside
world are at the borders between Plan 9 and reality. Within the
bounds of the system, compatibility with less discerning environments
is not an issue.

Is a web browser an exception? Maybe. Maybe not.

On the one hand, the point of the WWW is the first two WWs. On the
other hand, I'm sure there aren't that many people who can view
every site they visit with impunity.

So Plan 9 could only hope to reach a fraction of the sites. 10% of
the work might get you 90% of the sites, to a bearable degree. If they're
the 90% you want, it might be good enough to save you a reboot.

So I'm wondering if you take what the web has to offer - what people
try to show, in pages - and revisit it, from a Plan 9 viewpoint. Build
a Plan 9-only internal system, and translate at the boundary.



> The first real hard part is lexing/parsing the html in a way that is
> forgiving
> of errors in exactly the same ways as Netscape and IE.

I'm not that concerned. If I can work out what the content is supposed
to be, that'll do. "Exactly the same" is not an issue.

> The next real hard part
> is getting the layout (especially tables!)

But I'd hope that the internal system wouldn't use HTML (or at least,
not the outside version), but something else, more regular and predictable.
The table processing would be a single component of the translator.

> The hardest hard part is making Javascript objects and methods that behave
> exactly the same as Netscape and IE (especially if you want to do something
> different with respect to the concepts of "top level windows" or "frames").

Thoroughly unpleasant, yes. I'd be more inclined to live with frames (as
a supported concept at the translator) and dump javascript, though.

> And don't say "it doesn't have to be exactly the same as Netscape and IE"
> until you've had users.

But that all depends on the users, doesn't it? I've routinely got Java*
turned off. I don't have Flash, Shockwave, IE, Real* players, or any of
that rubbish. Personally, I get by without those sites. Others may not
be happy with that; they know where the solution lies. The same is true
for people who like MS Office, emacs, X, etc.

Perhaps this is being overly parochial. Everyone uses the Netscape and IE
features we know and loathe.

Everyone uses TCP, too. Plan 9 has IL.

steve




  parent reply	other threads:[~2000-07-19 19:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-18 15:38 miller
2000-07-18 17:31 ` Steve Kilbane
2000-07-19  9:27   ` Chris Locke
2000-07-19  9:27   ` Lyndon Nerenberg
2000-07-19 11:45     ` Howard Trickey
2000-07-19 12:27       ` Lucio De Re
2000-07-19 19:45       ` Steve Kilbane [this message]
2000-07-19 21:42         ` Boyd Roberts
2000-07-20 16:34       ` Lyndon Nerenberg
2000-07-21  8:33         ` Tom Ivar Helbekkmo
2000-07-19 15:38   ` Andy Newman
  -- strict thread matches above, loose matches on Subject: below --
2003-10-28 16:38 [9fans] Re: we need help matt
2003-11-11 17:12 ` [9fans] mothra Richard Miller
2000-07-19 18:29 rob pike
2000-07-19 16:59 Randolph Fritz
2000-07-19 12:05 Réf. : " boyd.roberts
2000-07-19 12:31 ` [9fans] " Howard Trickey
2000-07-19 12:51   ` [9fans] " Lucio De Re
2000-07-19 12:41     ` Colin DeVilbiss
2000-07-18 18:33 Russ Cox
2000-07-18 18:26 forsyth
2000-07-18 22:15 ` Randolph Fritz
2000-07-19  9:28   ` Chris Locke
2000-07-19 15:23     ` Andy Newman
2000-07-18 13:37 rob pike
2000-07-18 13:15 Sape Mullender
2000-07-18 16:25 ` Holger Veit
2000-07-18 12:51 rob pike
2000-07-18 13:19 ` Lucio De Re
2000-07-18 12:49 rob pike
2000-07-18 12:48 rob pike
2000-07-19 15:22 ` Douglas A. Gwyn
2000-07-17 13:49 boyd.roberts
2000-07-17 16:56 ` Tom Duff
2000-07-17 17:18   ` Howard Trickey
2000-07-18  8:25     ` Michael Jeffrey
2000-07-18  8:25   ` Douglas A. Gwyn
2000-07-18  8:58     ` Lucio De Re
2000-07-18 10:48       ` Wladimir Mutel
2000-07-18 11:37         ` Lucio De Re
2000-07-18 12:46           ` Wladimir Mutel
2000-07-19 15:23         ` Andy Newman
2000-07-18 18:11       ` Randolph Fritz
2000-07-19 15:22       ` Douglas A. Gwyn

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=200007192045.VAA15726@whitecrow.demon.co.uk \
    --to=steve@whitecrow.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).