News for hackers. Stuff that matters.
Re:Emacs Bytecode Internals (2014) by gus_massa on Tuesday December 27, 2016 @11:05AM (#13263882)
I think this is a difference in the point of view between the Java/C# word and the Lisp/Elisp/Scheme/Racket word.

In the Java/C# word, you are expected to get some libraries or shared code distributed as bytecode, without been able to see the source code. So the bytecode must ensure safety, so an application can run untrusted code.

[I'm more familiar with Racket.] In Lisp/Elisp/Scheme/Racket word you usually don't get shared code as bytecode, you get the source code. (An executable can be actually some bytecode packaged conveniently with the interpreter/JIT, but an executable can do whatever it likes, like formatting your hard disk.) So it's enough to ensure safety in the source code.

There are no comments on this comment yet.