Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.logic > #348358 > unrolled thread

How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop]

Back to article view | Back to sci.logic

Contents

  How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop] Mild Shock <janburse@fastmail.fm> - 2026-08-12 01:12 +0200
    Bullshit Authorized by Sarah Connor [EyeProlog Failure] (Re: How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop]) Mild Shock <janburse@fastmail.fm> - 2026-08-12 20:08 +0200
      Re: Bullshit Authorized by Sarah Connor [EyeProlog Failure] (Re: How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop]) Mild Shock <janburse@fastmail.fm> - 2026-08-12 20:17 +0200

#348358 — How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop]

Hi,

How fast is EyeProlog, do we need π-WAM?
Ok, here is a test:

between2(L, L, R) :- !, L = R.
between2(L, _, L).
between2(L, H, X) :- J is L+1, between2(J, H, X).

test :-
    between2(1, 100, _),
    between2(1, 100, _),
    between2(1, 100, _),
    fail.
test.

I get for EyeProlog and Dogelog:

/* EyeProlog */
0.476 sec
https://eyereasoner.github.io/eyeprolog/playground

/* Dogelog */
% Zeit 446.020 ms, GC 0.000 ms, Lips 6794 k
https://www.herbrand.ai/

Thats not bad. Now watch π-WAM, the first
AI accelerated Prolog subset, with
JavaScript Workers:

:- ensure_loaded(library(misc/brainfog)).

test2 :-
    execute((between(1,100,_),
             between(1,100,_),
             between(1,100,_))).

?- time(test2).
% Zeit 52.675 ms, GC 0.000 ms, Lips 9 k
true.

BTW: With JavaScript WebGPU the AI acceleration
is even an itch stronger, if the problem can
be parallelized.

Have Fun!

Bye

[toc] | [next] | [standalone]

#348361 — Bullshit Authorized by Sarah Connor [EyeProlog Failure] (Re: How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop])

Hi,

Its interesting that we already have
like for 50 years the Curry Howard
isomorphims, as proof justifications terms,

Still it seems extremly hard to generate
proof certificates for Prolog, isn't it?
How it started:

Ai x Big Gas. What could go wrong?
https://www.youtube.com/watch?v=kON2ZI2BNj8

How its going:

eq(Z,Z).
why eq(f(X,a),f(b,Y))
eq(f(b, a), f(b, a)).
why(
   eq(f(b, a), f(b, a)),
   proof(
     goal(eq(f(b, a), f(b, a))),
     by(fact("<input>", clause(1))),
     bindings([binding("Z", f(b, a))])
   )
).
https://eyereasoner.github.io/eyeprolog/playground

Truely some bullshit authorized by Sarah Connor.
So far there is no danger of an upcoming
Skynet that will gain self-awareness.

Bye

Mild Shock schrieb:
> Hi,
> 
> How fast is EyeProlog, do we need π-WAM?
> Ok, here is a test:
> 
> between2(L, L, R) :- !, L = R.
> between2(L, _, L).
> between2(L, H, X) :- J is L+1, between2(J, H, X).
> 
> test :-
>     between2(1, 100, _),
>     between2(1, 100, _),
>     between2(1, 100, _),
>     fail.
> test.
> 
> I get for EyeProlog and Dogelog:
> 
> /* EyeProlog */
> 0.476 sec
> https://eyereasoner.github.io/eyeprolog/playground
> 
> /* Dogelog */
> % Zeit 446.020 ms, GC 0.000 ms, Lips 6794 k
> https://www.herbrand.ai/
> 
> Thats not bad. Now watch π-WAM, the first
> AI accelerated Prolog subset, with
> JavaScript Workers:
> 
> :- ensure_loaded(library(misc/brainfog)).
> 
> test2 :-
>     execute((between(1,100,_),
>              between(1,100,_),
>              between(1,100,_))).
> 
> ?- time(test2).
> % Zeit 52.675 ms, GC 0.000 ms, Lips 9 k
> true.
> 
> BTW: With JavaScript WebGPU the AI acceleration
> is even an itch stronger, if the problem can
> be parallelized.
> 
> Have Fun!
> 
> Bye

[toc] | [prev] | [next] | [standalone]

#348362 — Re: Bullshit Authorized by Sarah Connor [EyeProlog Failure] (Re: How fast is EyeProlog, do we need π-WAM? [Budget AI Laptop])

Whoever payed for this nonsense, had his money
lavishly thrown out of a window. They could use the
australian gas to directly burn some dollar notes.

LoL

Mild Shock schrieb:
> Hi,
> 
> Its interesting that we already have
> like for 50 years the Curry Howard
> isomorphims, as proof justifications terms,
> 
> Still it seems extremly hard to generate
> proof certificates for Prolog, isn't it?
> How it started:
> 
> Ai x Big Gas. What could go wrong?
> https://www.youtube.com/watch?v=kON2ZI2BNj8
> 
> How its going:
> 
> eq(Z,Z).
> why eq(f(X,a),f(b,Y))
> eq(f(b, a), f(b, a)).
> why(
>    eq(f(b, a), f(b, a)),
>    proof(
>      goal(eq(f(b, a), f(b, a))),
>      by(fact("<input>", clause(1))),
>      bindings([binding("Z", f(b, a))])
>    )
> ).
> https://eyereasoner.github.io/eyeprolog/playground
> 
> Truely some bullshit authorized by Sarah Connor.
> So far there is no danger of an upcoming
> Skynet that will gain self-awareness.
> 
> Bye
> 
> Mild Shock schrieb:
>> Hi,
>>
>> How fast is EyeProlog, do we need π-WAM?
>> Ok, here is a test:
>>
>> between2(L, L, R) :- !, L = R.
>> between2(L, _, L).
>> between2(L, H, X) :- J is L+1, between2(J, H, X).
>>
>> test :-
>>     between2(1, 100, _),
>>     between2(1, 100, _),
>>     between2(1, 100, _),
>>     fail.
>> test.
>>
>> I get for EyeProlog and Dogelog:
>>
>> /* EyeProlog */
>> 0.476 sec
>> https://eyereasoner.github.io/eyeprolog/playground
>>
>> /* Dogelog */
>> % Zeit 446.020 ms, GC 0.000 ms, Lips 6794 k
>> https://www.herbrand.ai/
>>
>> Thats not bad. Now watch π-WAM, the first
>> AI accelerated Prolog subset, with
>> JavaScript Workers:
>>
>> :- ensure_loaded(library(misc/brainfog)).
>>
>> test2 :-
>>     execute((between(1,100,_),
>>              between(1,100,_),
>>              between(1,100,_))).
>>
>> ?- time(test2).
>> % Zeit 52.675 ms, GC 0.000 ms, Lips 9 k
>> true.
>>
>> BTW: With JavaScript WebGPU the AI acceleration
>> is even an itch stronger, if the problem can
>> be parallelized.
>>
>> Have Fun!
>>
>> Bye
> 

[toc] | [prev] | [standalone]

Back to top | Article view | sci.logic

csiph-web