delegates

Oversimplifying things (with a little bias): JavaScript object model is Linq/delegates/reflection (the very best parts of C#) without the hassle.

Instead they suddenly announced it in the middle of negotiations, without even telling their own delegates.

A native peer is a native object to which a normal object delegates via native methods.

Further, those 177 delegates can mint CA=True certificates for anyone they like and our browsers trust those subordinates by default.

There are a lot of abstractions like interfaces, delegates, etc, that exist to get certain logical patterns past the language's strictness.

Any of the 177 delegates are trusted to sign for any domain on the internet.

On disk caching delegates this to the OS, which is pretty good at it.

Second, we can tell how many entities we have to trust, and the author just counted them: Mozilla's 177 delegates.

The WMF intentionally delegates large parts of the governance of Wikipedia to the community and cannot autocratically come in and force change without community buy in.

Mesos delegates it back to the requestors, as I understand it.

> On disk caching delegates this to the OS, which is pretty good at it.

I like the idea if it only delegates to other classes.

A convenient addition the library would be a Seq/Hash that delegates to a "regular" List or Map without copying.

What is the "spirit manifested in the debates?" 55 delegates debated the provisions of the document, and they had 55 points of view.

Kind of in the same way that programming languages become bloated with concepts like "Object Factory Factories" and "Singletons" and delegates, etc.

See this article about "Microsoft's delegates"...