[e-lang] YAP: The first deployed object-capability public application platform

[stay]

On Wed, Oct 29, 2008 at 10:30 AM, Toby Murray
<toby.murray at comlab.ox.ac.uk> wrote:
> On Wed, 2008-10-29 at 16:48 +0000, Ben Laurie wrote:
>> On Wed, Oct 29, 2008 at 4:20 PM, Toby Murray
>> > A question for the Caja folks: Can I therefore write YAP gadgets in
>> > Cajita, which has always felt like a much nicer language than Caja to
>> > me?
>>
>> I think the answer is currently "no" but will soon be "yes". Right now
>> we don't have a way to switch between Cajita and Valija modes without
>> a flag to the compiler. We're thinking about how to fix that.
>
> On Wed, 2008-10-29 at 09:56 -0700, stay wrote:
>> You can certainly *write* it in cajita, but you won't get all of the
>> benefits yet--it'll still be treated as valija.
>
> Valija? What's that? (Sorry, I've not been following Caja development
> closely. All of my understanding comes from the June version of the spec
> document which I've not read now since.. June.)
>
> Is there a more up-to-date document to which I can refer to make sense
> of the above?

No, we haven't updated that document yet.  I intend to start on that this week.

> I thought that Cajita was a subset of everything else. How, then, would
> I not get the benefits of it? Is this Valija thing not a superset of
> Cajita or am I misreading "benefits" above?

Valija is a simulation of (very nearly) ES3.1 strict mode on top of
cajita.  A Valija program is rewritten *twice*, once from Valija to
Cajita, and again from Cajita to Javascript.  The intermediate
language we'd been calling Caja has been abandoned and "Caja" now
refers to the project as a whole.

If you write your code in Cajita and run it on YAP today, it will
(unnecessarily) be rewritten twice, so it will be slower.
-- 
Mike Stay
stay at google.com