From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <775b8d190702170116s3f813ca9g2838060ff2e14ba3@mail.gmail.com>
Date: Sat, 17 Feb 2007 20:16:40 +1100
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
In-Reply-To: <13ed6dec35f386652936b725015d6e04@coraid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <599f06db0702160634q4cf51e24x320b99e2ab94991a@mail.gmail.com>
	<13ed6dec35f386652936b725015d6e04@coraid.com>
Topicbox-Message-UUID: 11394676-ead2-11e9-9d60-3106f5b1d025

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
>