[lenkite]

Maybe when Common LISP gets its next standard and stops being a geezer on the deathbed ? The world has changed since 1994. So has the computing landscape. If a programming language is static for more than a human generation, then it cannot expect any sort of adoption.

[vindarel]

Implementations evolve and improve. https://lisp-journey.gitlab.io/blog/these-years-in-common-li...

I just learned today that another new GC for SBCL is in the works, with GC pauses under 100 microseconds.

[kagevf]

It's unlikely the ANSI standard will ever get updated - it's a very expensive process.

Python doesn't have a standard, but it has a canonical implementation, so maybe a "defacto standard". Not having an official standard didn't matter, though.

Common Lisp has defacto "standard libraries" for things like threading. Other things, such as async, are less clear (to me), but libraries do exist. Just because something isn't in the standard, though, doesn't mean it can't exist. Also, implementation such as SBCL pick up a lot of the slack, filling in some of the missing gaps.

[lenkite]

Python evolves through PEP's https://peps.python.org. Can you kindly correct my deplorable ignorance and point me to the Common LISP enhancement proposals ? Maybe I am missing something elementary.

[mepian]

They are here: https://cdr.common-lisp.dev/

[lenkite]

Last proposal in mid 2013 - which is a proposal to improve the proposal repo! Doesn't really inspire confidence in the language.

[mepian]

And? What has changed so much since 2013 that would require new proposals? Do you need the language to change every month? You keep moving goalposts, and I'm beginning to think that you’re not arguing in good faith here.

[lenkite]

Not sure what you mean by arguing in good faith as its a straightforward argument.

So much stuff has changed since 2013. Containerization, massive increase in concurrency, mobile platform explosion, etc. Where is the concurrency standard ? Are these 14 CDR's even implemented by CL implementations ? Can't find which CL implementation implements priority queue. Several of those CDR's don't even appear active.

[medo-bear]

i think it is more correct to say that machine learning saved python

https://lwn.net/Articles/843660/

[lenkite]

Really ? We are simply going to ignore the entire Python web-app landscape ? Django, Flask, Pyramid, etc. The deployments of those outnumber CL deployments by so many several orders of magnitude. No, ML didn't "save" Python. It only accelerated its usage further above all competitors.

[medo-bear]

Django and other web apps pale in comparison to Python's dominance in numerical computing. Im not saying they are not important, in fact I believe Python's use in areas other than math drove its adoption in the scientific community, and that one growth fed the other, but without ML there are far too many competitors to Python. However, almost everyone agrees thag py2->py3 was a mess. I like that when I run CL code written 10/20 years ago, and even older!, I dont have to worry too much if it is going to run today