4 ms·
In Midori, objects are capabilities. This is possible because type safety is enforced and an object's type cannot be forged. It's easy to imagine a capabilitie
by ridiculous_fish 10y ago
In Midori, objects are capabilities. This is possible because type safety is enforced and an object's type cannot be forged.
It's easy to imagine a capabilities system built around closures. For example, a capability to send on a socket could be an unforgeable closure that performs that sending. Are there any systems that work this way?
- andrewflnr 10y agoMore details on Midori: http://joeduffyblog.com/2015/11/03/blogging-about-midori/ http://joeduffyblog.com/2015/11/03/blogging-about-midori/ This is the first of several blog posts by one of the authors. I haven't read all of them, but liked what I read so far. Does anyone have other resources with more detail?
- chrisseaton 10y ago> objects are capabilities What does 'a capability' mean? People seem to use the term to mean everything from objects to threads.
- the_why_of_y 10y agoIn this context, it means the object capability model. https://en.wikipedia.org/wiki/Object-capability https://en.wikipedia.org/wiki/Object-capability Which can be used as the foundation of security. https://en.wikipedia.org/wiki/Capability-based_security https://en.wikipedia.org/wiki/Capability-based_security Relevant application in Midori: http://joeduffyblog.com/2015/11/10/objects-as-secure-capabilities/ http://joeduffyblog.com/2015/11/10/objects-as-secure-capabil...
- humanrebar 10y agoAs a counterpoint, people would make poor-man objects in ancient Fortran by using array indices instead of addresses to reference the object. And you could use integers and lots of conditionals to represent polymorphism. You'd have to ban all sorts of things to lock out developers from making their own custom object systems.