From: "James A. Robinson" <jim.robinson@stanford.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Gecko based web browser
Date: Wed, 19 Jul 2000 18:16:31 -0700 [thread overview]
Message-ID: <200007200116.VAA23739@cse.psu.edu> (raw)
In-Reply-To: Message from sah@borf.com of "Wed, 19 Jul 2000 18:52:45 EDT."References: <Pine.LNX.4.10.10007191849400.387-100000@linux.borf.com> <Pine.LNX.4.10.10007191849400.387-100000@linux.borf.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="x-unknown", Size: 2261 bytes --]
And who wants to 'catch up' anyway? =) I liked Linux back in 1992, when
I could actually understand the various components and how they worked
together. Now I look at the mess they've made of configuring xdm and I
get very frustrated.
I think the idea of authoring an n-part web browser would be fun,
and it would let people explore interesting concepts along the way.
Earlier someone said the usefulness of an fs-type web retrievel engine
was limited. I can appreciate the problems that might occur when dealing
with unusual status codes or SSL or HTTP Auth. But the idea of building
an engine that could automatically give you a proxy system or could
easily be hooked into different browsers is still interesting to me.
I do agree that the hard part is parsing/displaying the html, but it would
still be useful to have a retrieval mechanism that I could use from the
command line. In their latest book, K&P wrote about a stock-ticker they
grabbed off of Yahoo. They wrote a csv parser library to handle decoding
and displaying the html they grabbed off the url. I think it would be
cool to be able to just do something like
#!/bin/rc
echo 'http://finance.yahoo.com/q?s=lu&d=v1' > /mnt/web/new/get
cat /mnt/web/new/data | awk '{...}'
and run it to get
LU, 64½, +2.28%, 11,183,600
or whatever. It's a little more direct than a multi-stage approach of
running wget, putting the results in a temp file, parsing, and cleaning
up. You don't worry about the retrieval part, it just works. I just
happen to think that might be leveraged by other tools as well.
> of course, if we never rewrite anything from scratch...how will we ever
> find out what we did wrong, the first time?
>
> Rewriting apps isn't simply an exercise in futility. It provides the
> opportunity to incorporate new concepts, sans hacking old code.
>
>
> On Wed, 19 Jul 2000, Andrey Mirtchovski wrote:
>
> > "Douglas A. Gwyn" wrote:
> >
> > > For Chrissakes, if you insist on rolling all your own software you'll
> > > never catch up. Wouldn't it be better to have a functional Web
> > > browser on your preferred development platform than to have to keep
> > > switching platforms every time you need to access the Web?
next prev parent reply other threads:[~2000-07-20 1:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2000-07-18 20:23 miller
2000-07-18 22:07 ` Randolph Fritz
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 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-19 7:18 forsyth
2000-07-19 7:43 ` Lucio De Re
2000-07-19 7:58 ` Randolph Fritz
2000-07-19 15:23 ` Jonathan Sergent
2000-07-20 1:41 rob pike
2000-07-20 8:34 ` George Coulouris
2000-07-20 4:05 James A. Robinson
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
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=200007200116.VAA23739@cse.psu.edu \
--to=jim.robinson@stanford.edu \
--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).