There is no flesh and blood async Prolog! (Was: Dog Shit: Call my name "jan.ai")

Hi,
Somebody wrote:
 > Right, but what I’m saying is that with the
 > current implementation as a separate process,
 > running independently of the editor and only
 > communicating over the channel defined by the
 > protocol, the ability to have fine-grained
 > asynchronous communication is limited.
Not my problem not seeking the state of the art. You
need of course a Prolog system that is all flesh
and blood cooperative multitasking. If you want
to do a GUI in Prolog similar like JavaScript
does it now, or a native GUI adapter. And I don't
count Tau-Prolog, although they showed amazing
stuff. But not amazing enough, still based
on continuations, and not based on promises. Or then
async/await. I am not sure what SWI WASM now delivers?
SWI Tinker shows me errors talking about threads when
I use the query background execution feature and if I
abort. But people from cooperative multitasking tend
to not use the terminology "thread", they prefer to
talk about "tasks". Ciao Playground doesn't count either,
since their channels to a background worker can even
not process an interrupt correctly.
Bye
Mild Shock schrieb:

Hi,
 The fukkers stole my name:
 Jan - Local AI Assistant
https://github.com/menloresearch/jan
 Bye
 P.S.: Meanwhile I am struggling with Quantum Paper
whille doing a dark/light CSS. Look my light olive turned dark
olive, that is somewhere near chocolate or is it dog shit?
 P.P.S.: Just figured out yesterday that some browser defaults
are more Motif/OSF than Material/Google, aka Quantum Paper.