Actually that's the only bit confusing part of the documentation (which now everyone is quoting to troll Angular).

No. Please read this entire document on directives, which are a front-and-center feature of Angular: http://docs.angularjs.org/guide/directive. The transclusion snippet is pretty representative of this entire document.

Pity Google don't take the hint and make it more readable/understandable then.

It's really not so bad, I'm in no way an angular expert, but reading that passage (even out of context), is not beyond the realms of comprehension.

I think it says what it needs to say in the context of the surrounding information, no more, no less.

AFAIK CSS uses camelCase for variables.[1]

1: http://css-tricks.com/currentcolor/

Even if it only runs Chrome OS?

I'd be interested in it, developer mode gives access to vim and ssh, which is all I need to do my job (embedded kernel development). ChromeOS is quite decent on its own, and since it's ChromeOS it would have flash and their PDF reader on it. The only real complaint there is that their PDF reader doesn't support indexes and I usually have PDFs that are 2-5k pages so scrolling is a pain.

I don't find that post hilarious but good thing: they no longer need to do the dirty-checking in the latest Chrome[1], which will improve performance significantly.

1: https://plus.google.com/112439678898563138768/posts/RZKRBiGX...

>JPEG XR†, seems vastly superior to WebP in almost every way

No animations duh.

Is that really a problem? I would much prefer animated gifs never existed.

Boy, huge loss there... ><

Yes, it would be a big loss.

haha in-joke.

"During the trial, jurors were forced to watch hours of videos in which females engaged in sex acts involving human waste and animals."

Made me chuckle.

What's with the racist mentality?

Well you have no idea how much shit and limits I have to go through because of these sickos.

It might not be very safe at the moment, but this _is_ the future no matter how much you troll.

There's also Caja by Google: http://code.google.com/p/google-caja/

Caja and Narcissus are definitely comparable parallels, but Continuum is unique in that it fully implements the ECMAScript object model, runtime, and standard library (except for a few things which are still in progress). I would say that Continuum is the only one that qualifies to be called a "JavaScript engine" in its own right.

Narcissus is a meta-circular interpreter that puts a thin layer over the host engine, and requires that host engine itself to have some ES6 features (it can only actually run in Spidermonkey and V8 with the --harmony flag enabled).

Caja is more of a wrapper that protects access to capabilities than anything. In fact it specifically avoids fully parsing source code itself in order to be performant. Its goal is to sandbox code, not interpret it.

Continuum implements the ES6 Object Model and nearly fully implements the internal algorithms of the ~450 page ES6 specification (aside a small handful of things which are a bit out of date or remain to be implemented). In fact, the only thing it does not implement itself is RegExp, which it currently wraps the host engine's functionality to provide. It even fully implements the Date internal algorithms (https://github.com/Benvie/continuum/blob/gh-pages/engine/bui...).

Additionally, it self-hosts much of its own code. All of the ES6 standard library is itself written in ES6 (https://github.com/Benvie/continuum/tree/gh-pages/engine/bui...) and is executed in the virtual machine each time a realm is created. Roughly 25% of Continuum's code is written in ES6, while the other 75% is written in ES3 (I plan to reverse this ratio in time).

Also Tachyon is a full JS engine built in JS. It's incomplete but has the ability self-host itself and JIT compile machine code (all written in JS), so it gets bonus points to offset the fact that its implementation is incomplete https://github.com/Tachyon-Team/Tachyon