Nevertheless I have bad news for Prolog (Was: Scryer Prolog has dethroned SWI-Prolog)

Hi,
But doing the obvious right, is only solid engineering,
it doesn't lead to this advertisement:
testbed for bleeding edge research in logic and constraint programming
https://github.com/mthom/scryer-prolog
Also I doubt that this leads to anywhere, since we
live in a new era of subsymbolic AI and generative AI,
mostlikely pushing the boundaries of some symbolic pipe
dreams which have been anyway invalidated by computational
complexity research, without offering something really
innovative, i.e. only copy pasting SWI-Prolog including
nonsense like libray(sgml) mostlikely leads to nowhere.
Bye
Mild Shock schrieb:

Hi,
 Interestingly Scryer Prolog does many things right.
I find the following test case:
 /* Scryer Prolog 0.9.4-403 */
?- length(L,2), f(L) = R, S = [_A].
L = [_B, _C],
R = f([_B, _C]),
S = [_A].
 While SWI-Prolog still makes the following error. The
newly generated _A and _B are not checked whether they
already appear in the answer elsewhere, causing a name clash:
 /* SWI-Prolog 9.3.22 */
?- length(L,2), f(L) = R, S = [_A].
  = [_A, _B],
R = f([_A, _B]),
S = [_A].
 Other Prolog systems that avoid the clash as well are
Trealla Prolog, and since today Dogelog Player.
 Bye
 Mild Shock schrieb:

Hi,
>
It is time for the 2025 Prolog Awards.
Are you excited yet?
>
https://9gag.com/gag/aPAXyEP
>
Here is the list:
>
1. Place: Scryer Prolog, it uses rustyline,
very convenient:
>
app<tab>     gives append
a<tab><tab>  cycles through letter a predicates
length(foo)  shows the matching braket in blue
Etc..
>
-1. Place: SWI-Prolog, has no line edit at all
>
Bye