From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new links binary+source
Date: Thu, 18 Dec 2003 11:52:46 +0900 [thread overview]
Message-ID: <67f1d1312d5ee3af855f25c6ae8b86b6@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <4232834834cb615e6196fd51ce05806e@collyer.net>
> The fundamental structure of links is just wrong: it tries to simulate
> threads or processes sharing memory by using select to trigger
> functions when input arrives, and using a convention that upon
> completion of some activity, there's a always a `completion routine'
> to be called next, possibly by select. It would be better on Plan 9
> to just rfork a process for each http request and let it run to
> completion, but doing that may require doing considerable violence to
> links (not that I'm opposed to that ☺).
This statment is very specific, and constructive. ☺
Links is the first web browser which displays UTF-8 pages good
except of older Panel library based one which I personally made it.
I hope many Japanese web writer will begin to write their pages
by UTF-8.☺ To make it possible for JIS, S-JIS looks like ridiculous
to me, because only Japanese use those codes...
> A few of us are also looking at using webfs, at Russ's suggestion.
> The more we can move out of links, the better.
Sure, if we have better web browse, it better for all of us.
Kenji
next prev parent reply other threads:[~2003-12-18 2:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 21:03 mirtchov
2003-12-17 21:23 ` Axel Belinfante
2003-12-18 2:16 ` okamoto
2003-12-18 2:33 ` Geoff Collyer
2003-12-18 2:52 ` okamoto [this message]
2003-12-19 6:10 ` okamoto
2003-12-19 6:20 ` andrey mirtchovski
2003-12-19 6:41 ` okamoto
2003-12-19 14:15 ` mirtchov
2003-12-19 6:49 ` okamoto
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=67f1d1312d5ee3af855f25c6ae8b86b6@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).