News for hackers. Stuff that matters.
Re:A Road to Lisp: Which Lisp by PaulHoule on Friday July 17, 2026 @02:57PM (#48950997)
it compiles to bytecode but the bytecode engine is not that fast.

i had a phase when I was using PyPi a lot for branchy "old AI" kinds of workloads and felt it was an easy win but since then it has been either numpy or PIL or pytorch doing the heavy lifting or scripty stuff like uploading files to S3 where performance doesn't matter a lot.

I will grant that Common Lisp can be compiled to run amazingly quickly!

Re:A Road to Lisp: Which Lisp by BoingBoomTschak on Friday July 17, 2026 @03:35PM (#48951399)
What he probably meant is that compilation is available at runtime to the user, allowing you to JIT stuff at will.

This is how https://github.com/marcoheisig/Petalisp#why-is-petalisp-writ... and https://github.com/numcl/specialized-function can exist.

Re:A Road to Lisp: Which Lisp by pjmlp on Saturday July 18, 2026 @01:13AM (#48955418)
In Lisp (compile ...) produces machine code, with various optimisation flags available, depending on the implementation.