3 ms·

Well, if you're running on a typical processor than any process can use pointer arithmetic to access memory, so you still need some sort of low-level memory pro

by zeveb 10y ago

Well, if you're running on a typical processor than any process can use pointer arithmetic to access memory, so you still need some sort of low-level memory protection mechanism. On some hypothetical Lisp/high-level-language processor, that needn't be the case, of course, but I honestly don't think we'll ever see something like that again.

catnaroek 10y ago
> than any process can use pointer arithmetic to access memory, The damage this can potentially cause can be prevented using proof-carrying code.
- kr7 10y ago
  I'm not sure why you're being downvoted. Store applications as byte code or source code and use a trusted JIT to generate machine code. With a system-wide garbage collector and bounds checking you would have a memory safe single address space operating system.
rer 10y ago
> I honestly don't think we'll ever see something like that again. Why?
- Keyframe 10y ago
  Probably fragility and security issues in that type of system.
  - nickpsecurity 10y ago
    One of earlier works combining high-security and functional programming was a security kernel for Scheme48: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.4213 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.4... http://mumble.net/~jar/pubs/secureos/ http://mumble.net/~jar/pubs/secureos/ That was the Scheme mathematically-verified in VLISP project: https://en.wikipedia.org/wiki/PreScheme https://en.wikipedia.org/wiki/PreScheme There was also a mathematically-verified, Scheme CPU: http://www.cs.indiana.edu/pub/techreports/TR544.pdf http://www.cs.indiana.edu/pub/techreports/TR544.pdf I imagine combining even these three components into an integrated systems would provide a lot more security and availability than the average desktop. The simplicity of the CPU might also aid in producing a NonStop-like solution for five 9's availability.

by zeveb 10y ago

catnaroek 10y ago

> than any process can use pointer arithmetic to access memory, The damage this can potentially cause can be prevented using proof-carrying code.

kr7 10y ago
I'm not sure why you're being downvoted. Store applications as byte code or source code and use a trusted JIT to generate machine code. With a system-wide garbage collector and bounds checking you would have a memory safe single address space operating system.

rer 10y ago

> I honestly don't think we'll ever see something like that again. Why?

Keyframe 10y ago
Probably fragility and security issues in that type of system.
- nickpsecurity 10y ago
  One of earlier works combining high-security and functional programming was a security kernel for Scheme48: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.4213 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.37.4... http://mumble.net/~jar/pubs/secureos/ http://mumble.net/~jar/pubs/secureos/ That was the Scheme mathematically-verified in VLISP project: https://en.wikipedia.org/wiki/PreScheme https://en.wikipedia.org/wiki/PreScheme There was also a mathematically-verified, Scheme CPU: http://www.cs.indiana.edu/pub/techreports/TR544.pdf http://www.cs.indiana.edu/pub/techreports/TR544.pdf I imagine combining even these three components into an integrated systems would provide a lot more security and availability than the average desktop. The simplicity of the CPU might also aid in producing a NonStop-like solution for five 9's availability.