I wonder sometimes how the world would look like if lisp won and the unit od deployment was a lisp machine image, if that makes sense. How would a kubernetes optimized for lisp look like? How would AWS EC2 look like? etc.
We wouldn't have need such barbaric things in a lisp world. :p
Personally I think/hope they would have earlier discoveries / more broad usage of the deterministic systems like nix etc, which are built upon functional principles of immutability etc.
> Personally I think/hope they would have earlier discoveries / more broad usage of the deterministic systems like nix etc, which are built upon functional principles of immutability etc.
If memory serves, traditionally CCL (Clozure Common Lisp [0]) had better support for Windows but SBCL was unbeatable for speed. Does anyone know if that’s still the case?
* the SB-SIMD contrib now supports ARM64. (Thanks to Sylvia Harrington)
* AVX512 instructions are now supported on X86-64. (Thanks to Robert Smith and Arthur Miller)
* additional support for SIMD instructions on ARM64 and X86-64. (Thanks to Arthur Miller)
These seem like pretty awesome additions. Does anyone know how SIMD works in SBCL? Is this at the codegen layer? i.e. can it auto-vectorize or anything like that? Or are these intrinsics you have to explicitly ask for?
I wonder sometimes how the world would look like if lisp won and the unit od deployment was a lisp machine image, if that makes sense. How would a kubernetes optimized for lisp look like? How would AWS EC2 look like? etc.
Variable AWS is unbound.
We wouldn't have need such barbaric things in a lisp world. :p
Personally I think/hope they would have earlier discoveries / more broad usage of the deterministic systems like nix etc, which are built upon functional principles of immutability etc.
Maybe the world would be guix/Hurd!
Common lisp isn't functional in that sense.
> Personally I think/hope they would have earlier discoveries / more broad usage of the deterministic systems like nix etc, which are built upon functional principles of immutability etc.
Yeah, that, uh, doesn't sound like Lisp
If any SBCL dev is here, please add documentation for how to use the memory arena feature. The only doc is an very old proposal document.
If memory serves, traditionally CCL (Clozure Common Lisp [0]) had better support for Windows but SBCL was unbeatable for speed. Does anyone know if that’s still the case?
[0] https://ccl.clozure.com/
Looks like you use it explicitly?
https://github.com/sbcl/sbcl/tree/master/contrib/sb-simd
No auto-vectorization yet, but you may find this illuminating: https://www.stylewarning.com/posts/nbody
Great to see the project is still going strong, I kinda want to try CL but I always feel like I don't have a great use-case.
CL can be used pretty much anywhere nowadays, even on the web with ECL wasm compilation.
I have a todo list longer than the Tour de France I want to tackle first!
I'm going pretty deep on Lisp on accident - can anybody give me more context on this?
more context beyond the changelog? what would you like to know?
Great semver number