>>20no you fucking retard, lack of direct memory access does not give you perfect security. security is not just memory safety and exploits are not just about buffer overflows. and even if we're talking just about memory safety, your're are forgetting one simple fact: code written in Lisp might not have buffer overflows, but a runtime you use to execute this code might. I mean, check out basically any pwn2own - they often start by writing a javashit code that exploits a memory error in a browser's JS runtime, and then escalate. and it's not like javashit is the only language with buggy runtimes - there's a reason JRE updates so often, for example. if a runtime is ring 0, step 1 of exploit chain becomes also the final step because there's no need to escalate.