-
Notifications
You must be signed in to change notification settings - Fork 127
Status of Caja Project? #1986
Comments
Caja is maintained by three-ish engineers in their spare time, one of
The new sandboxed iframe that all browsers implement is good enough On Thu, Nov 19, 2015 at 1:07 PM, Paul Cody notifications@github.com wrote:
Mike Stay - metaweta@gmail.com |
Thanks for your comments and quick reply. Can you comment on compatibility with the closure compiler? I tried putting I wrote a quick Thanks, |
I don't know enough about that to comment. Mark, Kevin? On Fri, Nov 20, 2015 at 7:47 AM, Paul Cody notifications@github.com wrote:
Mike Stay - metaweta@gmail.com |
We should ask Felix... he did a lot of the initial compatibility work with closure. Unfortunately the way caja is written doesn't lend itself well to many of the closure optimizations although deaf code elimination should work. |
Sorry, it's been a while since I looked at that, I don't remember much On Sat, Nov 21, 2015 at 11:53 AM, Jasvir Nagra notifications@github.com
|
Closing this as it isn't something that needs action. Please send further questions to google-caja-discuss@googlegroups.com. |
Can the Caja developers comment on the state of the Caja project? A few concerning observations are:
In any case, I think the ideas behind Caja are still great and I'd like to see it continue and grow, but I'm wondering what's happening.
Thanks in advance,
Paul
The text was updated successfully, but these errors were encountered: