News for hackers. Stuff that matters.
Re:A Road to Lisp: Which Lisp by pjmlp on Friday July 17, 2026 @02:50PM (#48950916)
Except that CPython still misses on (compile .....) part, indeed holding the industry back.
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.
Re:A Road to Lisp: Which Lisp by guenthert on Saturday July 18, 2026 @04:56AM (#48956337)
Not sure about that. I rather think it's the very dynamic nature of Python (e.g. at run time one can add members to classes) which limits performance gains achievable by compilation. Iirc PyPy got to some five fold performance gain against CPython.

Common Lisp, as an example, makes some deliberate flexibility (and elegance) vs. performance trade-offs. I'd think to speed Python up more than PyPy could, one would have to sacrifice some of its features (some of those might not be all that popular or even desirable).

Nah, Python has its place. If its performance isn't adequate for the problem at hand, rewrite the bottlenecks in C++ and be done. LLMs should make that easy, no?

Re:A Road to Lisp: Which Lisp by pjmlp on Saturday July 18, 2026 @06:07AM (#48956647)
The dynamic excuse always misses out fully dynamic languages like Smalltalk, Self, among others have achieved, and how it got further exploited into JavaScript engines.

However CPython isn't even half way there to either Papyrus or GraalPy.

The community attitude to rewrite into C, C++, Rust, Zig, whatever, is exactly why Python will never be like other dynamic languages, and the dynamism excuse will always be used.

Thankfully at least GPU vendors see it otherwise, so if nothing else at least it will get JITs that speak GPU machine code.

Re:A Road to Lisp: Which Lisp by BoingBoomTschak on Saturday July 18, 2026 @07:35AM (#48957093)
> e.g. at run time one can add members to classes

Which is something that can be done in CLOS, though. And in a much more thought out fashion, as usual with the CLOS/MOP, cf https://www.lispworks.com/documentation/HyperSpec/Body/04_cf...