© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Oh, now I should have something on my conscience for not liking the
situation where a very small group controls the whole Common Lisp
ecosystem? I didn't even call anyone names, perhaps, I should have if
the result is the same.
If one doesn't like the choices I make for SBCL they are able take
their code to Clozure or even fork SBCL. With ASDF you can't. Every
publicly available library is using ASDF, each in subtly different
ways, there's no way for a competitor to emerge without an
insurmountable amount of effort.
I don't have anything on my conscience for saying
https:/
and
https:/
The only thing I regret is playing along with ASDF for too long,
updating it and helping test it.
Now, why do I take out my personal gripes on SBCL users by not
updating ASDF? Because it's not personal, because it affects other
people too. I can't count all the "I updated SBCL and something doesn't
work" because of new ASDF versions. I can't sign off on a third party
piece of code to have the same aspirations towards quality and
stability (that's reach, considering the high amount of recent
regressions in SBCL, sorry, we're trying).
If it were up to me I would have stopped bundling ASDF and let the
user decide which version to use and when to update. Unfortunately,
that's exactly the breaking thing against which I'm preaching here.
So, the other choice is to leave ASDF at its current version and let
the user update to a different one on their own.