From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] abaco and gmail
Date: Sat, 17 Feb 2007 20:16:40 +1100 [thread overview]
Message-ID: <775b8d190702170116s3f813ca9g2838060ff2e14ba3@mail.gmail.com> (raw)
In-Reply-To: <13ed6dec35f386652936b725015d6e04@coraid.com>
a tight coupling is transparent in (oz/any)inferno.
On 2/17/07, erik quanstrom <quanstro@coraid.com> wrote:
> i don't know how fgb is doing, but after reading the ecmascript spec, i was
> considerably less hopeful that i'd have the time to implement it. imho, the worst
> feature is that it requires having a runtime scanner and parser because javascript
> can generate code at runtime and call it. also, javascript requires that one map
> page elements to javascripts object model -- one can theoretically reference any
> element of a page from javascript.
>
> this tight coupling of the browser and javascript engine means that importing an
> engine doesn't sound like even less fun than writing one.
>
> on the other hand, perhaps this is an inspiration for a followon to acme.
> with the right model, it would be considerably more fun to implement.
>
> - erik
>
next prev parent reply other threads:[~2007-02-17 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 4:41 ron minnich
2007-02-16 8:17 ` Federico Benavento
2007-02-16 13:05 ` erik quanstrom
2007-02-16 8:25 ` Steve Simon
2007-02-16 13:26 ` erik quanstrom
2007-02-16 14:25 ` Gorka Guardiola
2007-02-16 14:29 ` erik quanstrom
2007-02-16 14:34 ` Gorka Guardiola
2007-02-16 14:52 ` erik quanstrom
2007-02-17 9:16 ` Bruce Ellis [this message]
2007-02-16 15:30 ` ron minnich
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=775b8d190702170116s3f813ca9g2838060ff2e14ba3@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--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).