Re: imagining a programming language with a capability calling convention

> None of the problems with those languages are with their mechanisms for
> calling or creation. As an ocap call mechanism, their calling mechanisms are
> all fine.

I always had it in my (thick, slow) head that
{java,javascript,ruby,c++,younameit}'s unrestricted (other than e.g.
class visibility modifiers, which aren't going to stop me from using
reflection anyway) 'new()' was bad ambient authority. I'd always
imagined that a "real" ocap system would have to pass around a Factory
(of Factories, or whatever).