stefankomatsu

CML is great and really deserves more attention.

We're lucky to have Andy deep dive into so many interesting subjects (modern JS engines, Concurrent ML), explain them in enthusiastic and well-written blog posts, and back it up with open source Scheme code.

In a previous blog post he name droped Mike Sperber; for reference, here is Mike's implementation of CML using Scheme 48's optimistic concurrency features: http://www.s48.org/cgi-bin/hgwebdir.cgi/s48/file/a4462425629.... I wonder if that was ever used for anything.

Appreciate your your answers. This makes Fuchsia quite interesting to me.

Thanks. How about virtualization? Using an example from the doc, if your child process accesses "/dev/class/framebuffer", can you intercept its communications? Can a process create a custom sandbox and run, say, AppMgr with limited permission to limit the permissions of all apps it manages?

> An empty process has nothing > Namespaces are the gateway to the world

Sounds like capability security to me. Although I wish they had said more about how these namespaces work. If they are inheritable and you can virtualize them for child processes (as you can in Plan 9/Inferno) then I'd say it qualifies.

Judging by nomenclature it seems to be more influenced by Plan 9, which also adhered somewhat to capability-based security without advertising that fact.