<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
There is value in when you are saying, Nicolas.<br>
<br>
Since Clozure Associates dissolved its LLC and its founders retired,<br>
it is now up to <u>us as a community</u> to carry the torch and
maintain CCL.<br>
There is no "somebody else" to do it for us. <br>
We all have to answer questions.<br>
We all have to fix bugs. <br>
We all have to make sure bug fixes are tested, checked in, and
patches created.<br>
There is an argument that a smaller "core" of maintainers oversee
releases,<br>
but if we keep adding to a regression suite and are diligent about
running it,<br>
anyone should be able to make a release, as long as they keep in
communication.<br>
Where "release" means a carefully curated and extensively tested
build.<br>
<br>
As for CCL's "demise being greatly exaggerated," I've been seeing
clear evidence that<br>
there is decreasing opportunity to run a viable business licensing
proprietary CLs.<br>
Open source Common Lisps are the way to go.<br>
My apologies to the maintainers of SBCL, but it is weighed down by
lots of pet projects.<br>
CCL is a highly optimized, complex-but-lean, "diamond."<br>
I back the "diamond" approach.<br>
<br>
<div class="moz-cite-prefix">On 1/5/24 2:13 PM, Nicolas Martyanoff
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:877cknh9uc.fsf@valhala.localdomain">
<pre class="moz-quote-pre" wrap="">Ron Garret <a class="moz-txt-link-rfc2396E" href="mailto:ron@flownet.com"><ron@flownet.com></a> writes:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Jan 5, 2024, at 5:41 AM, Tim McNerney <a class="moz-txt-link-rfc2396E" href="mailto:mc@media.mit.edu"><mc@media.mit.edu></a> wrote:
It's not too late to fix this flaw. What's the harm?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Bikeshedding. If we don't get the M1 port done, CCL is dead. We need to focus.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
While I have no doubt that not having a M1 port is a deal breaker for
developers working on MacOS, I would argue that the lack of regular
releases and the multitude of open issues and pull requests (i.e. the
lack of maintenance) is what is killing CCL.
Running on Apple Silicon is not going to fix the multitude of issues you
might encounter on any platform. As an example, a couple months ago I
try starting to write a patch for CCL, spent way too much time trying to
decipher code with no comment or type declaration, then realized that
CCL would randomly segfault when rebuilding itself (Linux/x86_64).
Google showed me at least one person having encountered the exact same
problem before, and zero answers. I went back to SBCL and will probably
drop CCL support from my projects because what is the point?
I fully understand that no one at Clozure has the time or money to
invest on CCL and I'm not blaming anyone; it is already admirable of
them to have built CCL and released it under a free license. But
This is just what happens in the Open Source world when no one forks an
unmaintained project, especially for a language which while not dead is
starting to smell really funny.
</pre>
</blockquote>
<br>
</body>
</html>