@civodul When I did a talk covering Guix to the #ScryerProlog community, I hung the theme on the importance of reproducability.
I focused on the analogy of Robert Boyle's formation of the 'experimental method':

https://en.wikipedia.org/wiki/Leviathan_and_the_Air-Pump

This was to emphasize the value of Guix wrt reproducibility and its disciplines (either scientific or artisanal) and how this is significant for logical programming domains like Prolog.

#Guix is unlike encapsulation of Microsoft and future haipe generated forms.

@paultarvydas Any chance of adding #ScryerProlog to this list?

They are active and have a lovely community.

@hako Thanks for your efforts.

(Ive probably mentioned this before) Im sitting on a very large #ScryerProlog package definition, which I held off publicising (in addition to dotting all the copyright of previous packagers).

https://github.com/mthom/scryer-prolog/discussions/2776#discussioncomment-13343885

As such /when/ I can reapproach it I will be able to provide some benchmarking/comparison for a very complex build :)

(from recollection its about 80k LOC avoiding Guix's centralised package definitions).

@yaxu I referenced some #ScryerProlog people. Some may be interested given their approaches to #ConstraintLogicProgramming and mixing disciplines

https://github.com/mthom/scryer-prolog/discussions/2849