5 ms·

Is there anything new, since.... say 2014? Anyone familiar with the project care to comment on how viable a sicl is today, as a common lisp?

by e12e 5y ago

rgrmrts 5y ago
I’ve been watching the project for a while, and have dropped into the irc channel a few times. From what I’ve gathered, there’s slow but steady progress. Last I checked SICL was in a usable state, but I’m not sure how production ready it is or if there are benchmarks available to compare it to, say, sbcl. The folks working on it are always super friendly and helpful, so if you’re curious to learn more I’d recommend dropping by their irc channel and asking.
eslaught 5y ago
I don't know anything about this specific implementation, but I find it incredible that the main author seems to be committing to the repo on a daily basis. Considering how old the project is, that's quite a commitment for any open source project, much less a CL implementation! But I agree it would be nice to get some information on how complete it is.
Twisol 5y ago
It's at least maintained enough for their README to be up to date as of the recent Freenode brouhaha: > All these channels are on the libera.chat network.
spiaggia 5y ago
SICL is definitely not "viable" today, in that we are still not at the stage where we can generate a native executable. But we are making good progress. Register allocation is close to being done. Code generation is next. We recently programmed ASDF so that it can participate in the bootstrapping procedure, so now, it will be easier to load additional libraries into the target environment, like Eclector, Clostrum, Trucler, Cleavir, and the systems they depend on. I am not going to be a regular participant here, so if you have any questions, it would be better to show up on the #sicl IRC channel on libera.chat.
chalst 5y ago
Some of the core ideas of SICL have been written up in a digestible form in a 2019 paper, 'Bootstrapping Common Lisp using Common Lisp' https://hal.archives-ouvertes.fr/hal-02417646/document https://hal.archives-ouvertes.fr/hal-02417646/document

Is there anything new, since.... say 2014? Anyone familiar with the project care to comment on how viable a sicl is today, as a common lisp?

by e12e 5y ago

Is there anything new, since.... say 2014? Anyone familiar with the project care to comment on how viable a sicl is today, as a common lisp?

rgrmrts 5y ago

I’ve been watching the project for a while, and have dropped into the irc channel a few times. From what I’ve gathered, there’s slow but steady progress. Last I checked SICL was in a usable state, but I’m not sure how production ready it is or if there are benchmarks available to compare it to, say, sbcl. The folks working on it are always super friendly and helpful, so if you’re curious to learn more I’d recommend dropping by their irc channel and asking.

eslaught 5y ago

I don't know anything about this specific implementation, but I find it incredible that the main author seems to be committing to the repo on a daily basis. Considering how old the project is, that's quite a commitment for any open source project, much less a CL implementation! But I agree it would be nice to get some information on how complete it is.

Twisol 5y ago

It's at least maintained enough for their README to be up to date as of the recent Freenode brouhaha: > All these channels are on the libera.chat network.

spiaggia 5y ago

SICL is definitely not "viable" today, in that we are still not at the stage where we can generate a native executable. But we are making good progress. Register allocation is close to being done. Code generation is next. We recently programmed ASDF so that it can participate in the bootstrapping procedure, so now, it will be easier to load additional libraries into the target environment, like Eclector, Clostrum, Trucler, Cleavir, and the systems they depend on. I am not going to be a regular participant here, so if you have any questions, it would be better to show up on the #sicl IRC channel on libera.chat.

chalst 5y ago

Some of the core ideas of SICL have been written up in a digestible form in a 2019 paper, 'Bootstrapping Common Lisp using Common Lisp' https://hal.archives-ouvertes.fr/hal-02417646/document https://hal.archives-ouvertes.fr/hal-02417646/document