<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
[When I write "I shouldn't be saying this," I should stop right
there. Likewise for "my apologies to"...]<br>
<br>
Hayley Patton <i>who comes highly recommended to us as a potential
contributor to CCL</i><br>
is the computer scientist who wrote the <a
href="https://zenodo.org/records/7816398">Concurrent GC for SBCL</a>
that you so highly praise.<br>
<br>
We would be <i>honored</i> if someone did something this hard and
integrated it into the CCL kernel.<br>
<br>
--Tim<br>
<br>
<div class="moz-cite-prefix">On 1/5/24 3:42 PM, Nicolas Martyanoff
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8734vbh5qr.fsf@valhala.localdomain">
<pre class="moz-quote-pre" wrap="">Tim McNerney <a class="moz-txt-link-rfc2396E" href="mailto:mc@media.mit.edu"><mc@media.mit.edu></a> writes:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Since Clozure Associates dissolved its LLC and its founders retired,
it is now up to _us as a community_ to carry the torch and maintain CCL.
There is no "somebody else" to do it for us.
We all have to answer questions.
We all have to fix bugs.
We all have to make sure bug fixes are tested, checked in, and patches created.
There is an argument that a smaller "core" of maintainers oversee releases,
but if we keep adding to a regression suite and are diligent about running it,
anyone should be able to make a release, as long as they keep in communication.
Where "release" means a carefully curated and extensively tested
build.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">I'm not disagreeing, but none of this is happening unless either Clozure
gives project admin right to someone really invested, or this someone
does the job of forking the project.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">As for CCL's "demise being greatly exaggerated," I've been seeing clear
evidence that
there is decreasing opportunity to run a viable business licensing proprietary
CLs.
Open source Common Lisps are the way to go.
My apologies to the maintainers of SBCL, but it is weighed down by lots of pet
projects.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Which projects are you refering to? I was pleasantly surprised by the
new optional concurrent GC recently released, this kind of initiative is
exactly what we need in the CL world.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">CCL is a highly optimized, complex-but-lean, "diamond."
I back the "diamond" approach.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Dropping all the MacOS UI code, the editor, cleaning the mess (I still
have headaches from what I've read on the FFI layer and error handling
in the IO layer) concentrating on standard compliance and robustness
would make it a diamond in time. The amount of work to get there is
staggering; I suspect writing a new implementation (with a decent
userland thread based runtime pretty please) would be less painful and
much more interesting.
But just patching bugs and releasing regularly would be nice.
</pre>
</blockquote>
<br>
</body>
</html>