Replies: 2 comments
-
As I'm not a git user (as I'm not a developer etc.) I won't try this challenge. But I like the idea of the synchronicity and the idea of using Prolog for data processing and analysis. And I would like to say that I like your new video Faster labeling for N-Queens/"Algorithm = Logic + Control" very much... I have the "Algorithm = Logic + Control" paper in PDF, yet, for me, your video is very inspirational, refreshing... It re-freshed my own perspective on Prolog, my own reasons why Prolog is so interesting, and why I want to use it (and study it) now and in the future. Thank you... |
Beta Was this translation helpful? Give feedback.
-
As I favour micro-commits and tend to make many mistakes, and retrace my steps frequently, this may represent an over-estimation of my work ethic. |
Beta Was this translation helpful? Give feedback.
-
Dear all,
Scryer Prolog and Trealla Prolog by @infradig, two Prolog systems that both started several years ago, are implemented in different languages, and have significant overlap and also differences in direction of ambition and features, currently have almost the same number of commits!
In fact when I looked a few days, they had the exact same number of commits!
And this is a challenge I would like to pose today: Write a Prolog program that determines all time ranges where these two projects had the exact same number of commits. Start with the dates of commits as Prolog facts. You can generate such facts for example with:
Yielding, for Scryer Prolog:
All the best,
Markus
Beta Was this translation helpful? Give feedback.
All reactions