heisig

7 ms·

31.
by heisig 6y ago
First class global environments are not about having multiple users on the same machine. Their main purpose is isolation, sandboxing, and reproducibility. Not every program should be able to modify the compiler, the kernel, or the garbage
32.
by heisig 6y ago
> why not design a new Lisp? Hell no. Here is why: 1. The Common Lisp standard is brilliant. If your new Lisp is designed by anything less than a committee with people like Kent Pitman, Guy Steele, and Richard P. Gabriel, chances are t
33.
by heisig 6y ago
There is an active and growing group of hackers trying to make CLOSOS a reality. The current progress can be viewed at https://github.com/robert-strandh/sicl (SICL is the Common Lisp implementation that will be used
34.
by heisig 7y ago
Let me chip in here to clarify some things. > other languages, just as dynamic, like Common Lisp and Smalltalk, have quite capable JIT compilers. Common Lisp implementations don't need a JIT compiler to be fast. In fact, most of th
35.
by heisig 7y ago
Even better, the first few multiple values are typically returned in CPU registers and not on the stack.
36.
by heisig 7y ago
> What happened to Common Lisp? Common Lisp is probably in its best shape ever. There is finally a good package manager ( https://www.quicklisp.org/ ), plenty of documentation ( https://common-lisp.net/docu
37.
by heisig 7y ago
There are still people explaining to me why you need a 'system programming language' like C or Rust for certain tasks. Meanwhile, I'm playing a game of Quake on Mezzano, where everything from drivers to the actual videogame
38.
by heisig 7y ago
The points for Common Lisp are: 1. It is ANSI standardized and mature. 2. Common Lisp programs are safe. Some implementations violate safety for performance reasons, but this one certainly won't. 3. Common Lisp has the best error hand
39.
by heisig 7y ago
Summary: - We don't need separate processes if the language we use is inherently safe (e.g., modern Common Lisp). - Without process isolation, it is possible to share large, complicated and possibly mutable data structures (graphs, arr