diff options
| -rw-r--r-- | Proposal.md | 4 | ||||
| -rw-r--r-- | bibliography.bib | 8 |
2 files changed, 12 insertions, 0 deletions
diff --git a/Proposal.md b/Proposal.md index ebb07fc..99fa7b5 100644 --- a/Proposal.md +++ b/Proposal.md @@ -107,6 +107,10 @@ Why not a unified permission system? seL4 => uses identifiers as keys for the capabilities +3L project[@3L:Hintz] => many ideas are the same that we have but it doesn't +embrace the language in the sense it affects how the processor is built (to +help the interpreter). It's written in pre-scheme instead. + Use an interpreted language and give capabilities as functions in an environment: they can be mocked! Or manipulated! Or executed remotely in a distributed fashion! diff --git a/bibliography.bib b/bibliography.bib index a9abddd..c2392a2 100644 --- a/bibliography.bib +++ b/bibliography.bib @@ -63,3 +63,11 @@ doi={10.1109/SPW50608.2020.00039} } % https://www.contrib.andrew.cmu.edu/~somlo/BTCP/ + +@misc{ 3L:Hintz, + title = {3L: The Computing System of the Future}, + author = {Thomas Hintz}, + year = 2016, + note = {Accessed: 2024-06-20}, + howpublished = {\url{https://3lproject.org/}} +} |