• Re: The road to Artificial Intelligence

    From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Sun Jun 4 07:49:19 2023
    From Newsgroup: comp.lang.prolog


    Your new Scrum Master is here! - ChatGPT, 2023 https://www.bbntimes.com/companies/ai-will-make-agile-coaches-and-scrum-masters-redundant-in-less-than-2-years

    LoL

    Thomas Alva Edison schrieb am Dienstag, 10. Juli 2018 um 15:28:05 UTC+2:
    Prolog Class Signpost - American Style 2018 https://www.youtube.com/watch?v=CxQKltWI0NA
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Jun 20 08:20:25 2023
    From Newsgroup: comp.lang.prolog

    To hell with GPUs. Here come the FPGA qubits:
    Iran’s Military Quantum Claim: It’s Only 99.4% Ridiculous https://hackaday.com/2023/06/15/irans-quantum-computing-on-fpga-claim-its-kinda-a-thing/
    The superposition property enables a quantum computer
    to be in multiple states at once. https://www.techtarget.com/whatis/definition/qubit
    Maybe their new board is even less suited for hitting
    a ship with a torpedo than some machine learning?
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Wed Jun 21 03:24:00 2023
    From Newsgroup: comp.lang.prolog

    So it begins:

    Was having some fun with chat gpt and thinkscript. https://twitter.com/pkay2402/status/1670459050155290627

    A Beginner's Guide to thinkScripts - Ameritrade, 2022 https://www.youtube.com/watch?v=qD5RYF5o9fM
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Fri Jun 23 02:14:13 2023
    From Newsgroup: comp.lang.prolog

    Not only the speed doesn't double every year anymore,
    also the density of transistors doesn't double
    every year anymore. See also:
    ‘Moore’s Law’s dead,’ Nvidia CEO https://www.marketwatch.com/story/moores-laws-dead-nvidia-ceo-jensen-says-in-justifying-gaming-card-price-hike-11663798618
    So there is some hope in FPGAs. The article writes:
    "In the latter paper, which includes a great overview of
    the state of the art, Pilch and colleagues summarize
    this as shifting the processing from time to space —
    from using slow sequential CPU processing to hardware
    complexity, using the FPGA’s configurable fabric
    and inherent parallelism."
    In reference to (no pay wall):
    An FPGA-based real quantum computer emulator
    15 December 2018 - Pilch et al. https://link.springer.com/article/10.1007/s10825-018-1287-5
    Mild Shock schrieb am Dienstag, 20. Juni 2023 um 17:20:27 UTC+2:
    To hell with GPUs. Here come the FPGA qubits:

    Iran’s Military Quantum Claim: It’s Only 99.4% Ridiculous https://hackaday.com/2023/06/15/irans-quantum-computing-on-fpga-claim-its-kinda-a-thing/

    The superposition property enables a quantum computer
    to be in multiple states at once. https://www.techtarget.com/whatis/definition/qubit

    Maybe their new board is even less suited for hitting
    a ship with a torpedo than some machine learning?
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Sat Jun 24 15:25:12 2023
    From Newsgroup: comp.lang.prolog

    Prighozin / Prighozout . Latest news he departed for Belarus?!
    Help! I need ChatGPT Plus to follow this shit show:

    Scraper is an excellent #ChatGPT plugin for staying on top of the news. https://twitter.com/irock/status/1672665497140330496

    Now, you can use the same info and make a diagram out of it. Using 'diagrams' plugin.
    https://twitter.com/irock/status/1672715014271115266

    But ChatGPT Plus is like 20$ per Month extra.
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Sat Jul 29 17:58:31 2023
    From Newsgroup: comp.lang.prolog

    Omg, Stephen Wolfram wrote a new book!

    What Is ChatGPT Doing ... and Why Does It Work? https://www.amazon.com/dp/1579550819

    Did he let ChatGPT write the book, or why was he so fast?
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Aug 1 06:48:30 2023
    From Newsgroup: comp.lang.prolog

    How it started:
    Remember in 2013 a failed AI stack attemp, people making fun:
    Faked Artificial Intelligence like in Game Development https://area51.meta.stackexchange.com/q/11658/100686
    How its going:
    Take notd in 2023 sounds like total paniking now:
    Announcing OverflowAI, Projects: a bunch of crap, Slack
    chatbot and We’ve launched the GenAI Stack Exchange site https://stackoverflow.co/labs/
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Aug 1 06:54:29 2023
    From Newsgroup: comp.lang.prolog

    This is also quite memorable:
    "Don't give it a 'Hollywood' title like 'artificial intelligence'.
    Call it "Machine Learning and Intelligent Computation"". https://area51.meta.stackexchange.com/a/13109/100686
    LoL
    Mild Shock schrieb am Dienstag, 1. August 2023 um 15:48:32 UTC+2:
    How it started:

    Remember in 2013 a failed AI stack attemp, people making fun:
    Faked Artificial Intelligence like in Game Development https://area51.meta.stackexchange.com/q/11658/100686

    How its going:

    Take notd in 2023 sounds like total paniking now:
    Announcing OverflowAI, Projects: a bunch of crap, Slack
    chatbot and We’ve launched the GenAI Stack Exchange site https://stackoverflow.co/labs/
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Aug 1 07:31:52 2023
    From Newsgroup: comp.lang.prolog


    There is a serious doubt that there will be a surge
    in developers, due to AI. As claimed here:
    Stack Overflow: Community and AI https://www.youtube.com/live/g5F5t205pYA?feature=share&t=376
    Its rather in the end about low code as well:
    "These tools enable less technical employees to
    make a larger business impact in numerous ways,
    such as relieving IT department backlogs, reducing
    shadow IT, and taking more ownership over
    business process management (BPM) workstreams. https://www.ibm.com/topics/low-code
    LoL
    Mild Shock schrieb am Dienstag, 1. August 2023 um 15:54:31 UTC+2:
    This is also quite memorable:

    "Don't give it a 'Hollywood' title like 'artificial intelligence'.
    Call it "Machine Learning and Intelligent Computation"". https://area51.meta.stackexchange.com/a/13109/100686

    LoL
    Mild Shock schrieb am Dienstag, 1. August 2023 um 15:48:32 UTC+2:
    How it started:

    Remember in 2013 a failed AI stack attemp, people making fun:
    Faked Artificial Intelligence like in Game Development https://area51.meta.stackexchange.com/q/11658/100686

    How its going:

    Take notd in 2023 sounds like total paniking now:
    Announcing OverflowAI, Projects: a bunch of crap, Slack
    chatbot and We’ve launched the GenAI Stack Exchange site https://stackoverflow.co/labs/
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Wed Aug 2 02:02:03 2023
    From Newsgroup: comp.lang.prolog


    Experiment by Terrence Tao using ChatGPT - June, 2023 https://mathstodon.xyz/@tao/110601051375142142

    by way of Rainer Rosenthal on de.sci.mathematik
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Wed Aug 2 02:14:24 2023
    From Newsgroup: comp.lang.prolog


    Simple theory why stackoverflow is dead. Most
    of the answers on stackoverflow are any RTFM answers.
    And LLM that has done its homework, indexing all
    the fucking manuals, performs as well, there is no
    need for the "experts" on stackoverflow that are anyway
    not real "experts", mostly they are people who can read
    and know the relevant sources, they don't recall
    solutions from some genuine memory. So I guess
    this intermediary, this middleman stackoverflow,
    is not needed in the future. ChatGPT and similar
    bots will serve as ready help for those too lazy.
    And we are all lazy, aren't we?
    Abbreviation for ‘Read The Fucking Manual’. http://www.catb.org/jargon/html/R/RTFM.html
    Mild Shock schrieb am Mittwoch, 2. August 2023 um 11:02:05 UTC+2:
    Experiment by Terrence Tao using ChatGPT - June, 2023 https://mathstodon.xyz/@tao/110601051375142142

    by way of Rainer Rosenthal on de.sci.mathematik
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Wed Aug 2 02:20:15 2023
    From Newsgroup: comp.lang.prolog


    Or a hybrid, a stackoverflow with a chatbots integrated.
    ChatGPT is already helping me designing such a platform:
    Q: What if a chatbot becomes just a member of a community,
    this would assure collaboration and community interaction.
    A: Incorporating a chatbot as a member of an online community
    can indeed offer some benefits in terms of collaboration and
    community interaction. However, there are several
    considerations to take into account:
    [...]
    https://chat.openai.com/share/84790b3f-e228-4c91-af89-29cf37842f9d
    LoL
    Mild Shock schrieb am Mittwoch, 2. August 2023 um 11:14:26 UTC+2:
    Simple theory why stackoverflow is dead. Most
    of the answers on stackoverflow are any RTFM answers.
    And LLM that has done its homework, indexing all

    the fucking manuals, performs as well, there is no
    need for the "experts" on stackoverflow that are anyway
    not real "experts", mostly they are people who can read

    and know the relevant sources, they don't recall
    solutions from some genuine memory. So I guess
    this intermediary, this middleman stackoverflow,

    is not needed in the future. ChatGPT and similar
    bots will serve as ready help for those too lazy.
    And we are all lazy, aren't we?

    Abbreviation for ‘Read The Fucking Manual’. http://www.catb.org/jargon/html/R/RTFM.html
    Mild Shock schrieb am Mittwoch, 2. August 2023 um 11:02:05 UTC+2:
    Experiment by Terrence Tao using ChatGPT - June, 2023 https://mathstodon.xyz/@tao/110601051375142142

    by way of Rainer Rosenthal on de.sci.mathematik
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Aug 15 07:34:30 2023
    From Newsgroup: comp.lang.prolog

    Want to know what ChatGPT thinks about a person. Try this
    prompt engineering, works also with less prominent persons:

    Q: Write a joke: Why did Jan Wielemaker go to the gym

    A: Why did Jan Wielemaker go to the gym? Because he
    heard it was the only place with enough "SWI-t"ness to lift his spirits!

    https://chat.openai.com/?model=text-davinci-002-render-sha
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Sat Sep 23 13:51:11 2023
    From Newsgroup: comp.lang.prolog


    Now its clear, the Corona vaccine has had a side effect,
    everbody got Alzheimer over the last months. The
    SWI-Prolog discourse is a typical example, it has become

    a retirement home for some self-talking veterans.

    Thomas Alva Edison schrieb am Dienstag, 10. Juli 2018 um 15:28:05 UTC+2:
    Prolog Class Signpost - American Style 2018 https://www.youtube.com/watch?v=CxQKltWI0NA
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Wed Sep 27 04:05:59 2023
    From Newsgroup: comp.lang.prolog

    Don't do the LIPS.

    /* SWI-Prolog 9.1.16 */
    ?- time(tarai(12, 11, 0, X)).
    % 54,182,800 inferences, 2.625 CPU in 2.616 seconds (100% CPU, 20641067 Lips)
    X = 12.

    /* Guarded Horn Clauses */
    $ ./tarai 12 11 0
    % 196412655 inferences, 3.34256 CPU seconds (58761215.967661 Lips)
    12

    tadashi9e, 2023
    https://qiita.com/tadashi9e/items/45cef62cda6d38dda0c7

    Sanity No More - Only Chaos Here

    Mild Shock schrieb am Samstag, 23. September 2023 um 22:51:13 UTC+2:
    Now its clear, the Corona vaccine has had a side effect,
    everbody got Alzheimer over the last months. The
    SWI-Prolog discourse is a typical example, it has become

    a retirement home for some self-talking veterans.
    Thomas Alva Edison schrieb am Dienstag, 10. Juli 2018 um 15:28:05 UTC+2:
    Prolog Class Signpost - American Style 2018 https://www.youtube.com/watch?v=CxQKltWI0NA
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Wed Sep 27 05:36:33 2023
    From Newsgroup: comp.lang.prolog

    Unfortunately I find nowhere the full source of this new
    GHC Prolog by tadashi9e, which makes it a little dubious.
    Then Dogelog Player yet generates another number:

    tarai(X, Y, _, R) :- X =< Y, !, R = Y.
    tarai(X, Y, Z, R) :- X_1 is X-1, tarai(X_1, Y, Z, R_X),
    Y_1 is Y-1, tarai(Y_1, Z, X, R_Y),
    Z_1 is Z-1, tarai(Z_1, X, Y, R_Z),
    tarai(R_X, R_Y, R_Z, R).

    ?- statistics(calls, A), shield(tarai(12, 11, 0, _)), statistics(calls, B), C is B-A.
    A = 115190487, B = 230328953, C = 115138466.

    ?- statistics(calls, A), tarai(12, 11, 0, _), statistics(calls, B), C is B-A.
    A = 46911, B = 115187678, C = 115140767.

    shield/1 does switch off auto-yield. Expectation was rather
    that the second query gives 115138466 again, minus a few
    inferences since shield/1 wasn't called. But it seems that

    auto-yield leads to some phantom inferences which should
    not be the case. So I guess we have a glitch somehere in the
    bookkeeping. But why is GHC Prolog count higher? Maybe

    because it has some constructs like (->)/2 in the second clause
    of tarai. Also both clauses in GHC need (|)/2, and the second
    clause has a true/0 guard. This could explain the higher count?

    Mild Shock schrieb am Mittwoch, 27. September 2023 um 13:06:01 UTC+2:
    Don't do the LIPS.

    /* SWI-Prolog 9.1.16 */
    ?- time(tarai(12, 11, 0, X)).
    % 54,182,800 inferences, 2.625 CPU in 2.616 seconds (100% CPU, 20641067 Lips)
    X = 12.

    /* Guarded Horn Clauses */
    $ ./tarai 12 11 0
    % 196412655 inferences, 3.34256 CPU seconds (58761215.967661 Lips)
    12

    tadashi9e, 2023
    https://qiita.com/tadashi9e/items/45cef62cda6d38dda0c7

    Sanity No More - Only Chaos Here
    Mild Shock schrieb am Samstag, 23. September 2023 um 22:51:13 UTC+2:
    Now its clear, the Corona vaccine has had a side effect,
    everbody got Alzheimer over the last months. The
    SWI-Prolog discourse is a typical example, it has become

    a retirement home for some self-talking veterans.
    Thomas Alva Edison schrieb am Dienstag, 10. Juli 2018 um 15:28:05 UTC+2:
    Prolog Class Signpost - American Style 2018 https://www.youtube.com/watch?v=CxQKltWI0NA
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Oct 3 04:37:13 2023
    From Newsgroup: comp.lang.prolog


    So what is the issue that should be solved proactively.
    A single person cannot indefinitely maintain a Prolog system.
    Why? Not because the person will be dead at some time in

    the future, the person might also get unable to continue
    naintaining a Prolog system. Same holds for a community,
    it cannot age indefinitely. See also:

    Memory Loss, Alzheimer's Disease and Dementia, 3rd Edition
    by Andrew E. Budson, MD and Paul R. Solomon, PhD https://evolve.elsevier.com/cs/product/9780323795449

    So what are the option? Exit strategies? Generational change
    strategies? Where are the youngsters that will take over?
    This is a call for action, for people < 30 years old:

    - Please show us your Prolog interpreter

    Mild Shock schrieb am Samstag, 23. September 2023 um 22:51:13 UTC+2:
    Now its clear, the Corona vaccine has had a side effect,
    everbody got Alzheimer over the last months. The
    SWI-Prolog discourse is a typical example, it has become

    a retirement home for some self-talking veterans.
    Thomas Alva Edison schrieb am Dienstag, 10. Juli 2018 um 15:28:05 UTC+2:
    Prolog Class Signpost - American Style 2018 https://www.youtube.com/watch?v=CxQKltWI0NA
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Oct 3 04:54:07 2023
    From Newsgroup: comp.lang.prolog


    Could we say if life expectancy increases, senescence increases
    as well? Not sure. Senescence (/sɪˈnɛsəns/) or biological aging is the gradual deterioration of functional characteristics in living organisms.
    BTW: Here A Chapter in Idiotic Gurus: Where is Dementia?
    What if you your "Prana" goes missing via Dementia?
    Secrets Revealed : 5 Stages of Death https://www.youtube.com/watch?v=ZncdonlR5q8
    Unfortunately this lunatic is quite popular, India and USA etc..:
    New York Times bestsellers Inner Engineering: A Yogi's Guide to Joy https://en.wikipedia.org/wiki/Sadhguru
    Mild Shock schrieb am Dienstag, 3. Oktober 2023 um 13:37:15 UTC+2:
    So what is the issue that should be solved proactively.
    A single person cannot indefinitely maintain a Prolog system.
    Why? Not because the person will be dead at some time in

    the future, the person might also get unable to continue
    naintaining a Prolog system. Same holds for a community,
    it cannot age indefinitely. See also:

    Memory Loss, Alzheimer's Disease and Dementia, 3rd Edition
    by Andrew E. Budson, MD and Paul R. Solomon, PhD https://evolve.elsevier.com/cs/product/9780323795449

    So what are the option? Exit strategies? Generational change
    strategies? Where are the youngsters that will take over?
    This is a call for action, for people < 30 years old:

    - Please show us your Prolog interpreter
    Mild Shock schrieb am Samstag, 23. September 2023 um 22:51:13 UTC+2:
    Now its clear, the Corona vaccine has had a side effect,
    everbody got Alzheimer over the last months. The
    SWI-Prolog discourse is a typical example, it has become

    a retirement home for some self-talking veterans.
    Thomas Alva Edison schrieb am Dienstag, 10. Juli 2018 um 15:28:05 UTC+2:
    Prolog Class Signpost - American Style 2018 https://www.youtube.com/watch?v=CxQKltWI0NA
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Mon Nov 20 05:23:52 2023
    From Newsgroup: comp.lang.prolog

    Ok, OpenAI is dead. But we need to get out of the claws
    of the computing cloud. We need the spirit of Niklaus
    Wirth, who combined computer science and
    electronics. We need to solve the problem of
    parallel slilicon. Should have a look again at these
    quantum computers. Can we have them on the Edge?
    Mild Shock schrieb am Freitag, 23. Juni 2023 um 11:14:15 UTC+2:
    Not only the speed doesn't double every year anymore,
    also the density of transistors doesn't double
    every year anymore. See also:

    ‘Moore’s Law’s dead,’ Nvidia CEO https://www.marketwatch.com/story/moores-laws-dead-nvidia-ceo-jensen-says-in-justifying-gaming-card-price-hike-11663798618

    So there is some hope in FPGAs. The article writes:

    "In the latter paper, which includes a great overview of
    the state of the art, Pilch and colleagues summarize
    this as shifting the processing from time to space —
    from using slow sequential CPU processing to hardware
    complexity, using the FPGA’s configurable fabric
    and inherent parallelism."

    In reference to (no pay wall):

    An FPGA-based real quantum computer emulator
    15 December 2018 - Pilch et al. https://link.springer.com/article/10.1007/s10825-018-1287-5
    Mild Shock schrieb am Dienstag, 20. Juni 2023 um 17:20:27 UTC+2:
    To hell with GPUs. Here come the FPGA qubits:

    Iran’s Military Quantum Claim: It’s Only 99.4% Ridiculous https://hackaday.com/2023/06/15/irans-quantum-computing-on-fpga-claim-its-kinda-a-thing/

    The superposition property enables a quantum computer
    to be in multiple states at once. https://www.techtarget.com/whatis/definition/qubit

    Maybe their new board is even less suited for hitting
    a ship with a torpedo than some machine learning?
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Mon Nov 20 09:01:27 2023
    From Newsgroup: comp.lang.prolog


    Seems that OpenAI is effectively imploding. Any
    actors that wanted this had easy play because there
    were two tribes in OpenAI, namely the AI doomers
    and the AI futurists. Who cares? The AI doomers
    were possibly anyway those contributing less and
    will now end on the streets, a nice little shake out!
    Sutskever Regret and the Weekend That Changed AI https://www.youtube.com/watch?v=dyakih3oYpk
    Mild Shock schrieb am Montag, 20. November 2023 um 14:23:55 UTC+1:
    Ok, OpenAI is dead. But we need to get out of the claws
    of the computing cloud. We need the spirit of Niklaus
    Wirth, who combined computer science and

    electronics. We need to solve the problem of
    parallel slilicon. Should have a look again at these
    quantum computers. Can we have them on the Edge?
    Mild Shock schrieb am Freitag, 23. Juni 2023 um 11:14:15 UTC+2:
    Not only the speed doesn't double every year anymore,
    also the density of transistors doesn't double
    every year anymore. See also:

    ‘Moore’s Law’s dead,’ Nvidia CEO https://www.marketwatch.com/story/moores-laws-dead-nvidia-ceo-jensen-says-in-justifying-gaming-card-price-hike-11663798618

    So there is some hope in FPGAs. The article writes:

    "In the latter paper, which includes a great overview of
    the state of the art, Pilch and colleagues summarize
    this as shifting the processing from time to space —
    from using slow sequential CPU processing to hardware
    complexity, using the FPGA’s configurable fabric
    and inherent parallelism."

    In reference to (no pay wall):

    An FPGA-based real quantum computer emulator
    15 December 2018 - Pilch et al. https://link.springer.com/article/10.1007/s10825-018-1287-5
    Mild Shock schrieb am Dienstag, 20. Juni 2023 um 17:20:27 UTC+2:
    To hell with GPUs. Here come the FPGA qubits:

    Iran’s Military Quantum Claim: It’s Only 99.4% Ridiculous https://hackaday.com/2023/06/15/irans-quantum-computing-on-fpga-claim-its-kinda-a-thing/

    The superposition property enables a quantum computer
    to be in multiple states at once. https://www.techtarget.com/whatis/definition/qubit

    Maybe their new board is even less suited for hitting
    a ship with a torpedo than some machine learning?
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Sat Nov 25 07:23:05 2023
    From Newsgroup: comp.lang.prolog

    How my Dogelog Player garbage collector works:

    Ashes to ashes, funk to funky
    We know Major Tom's a junkie
    Strung out in heaven's high
    Hitting an all-time low
    https://www.youtube.com/watch?v=CMThz7eQ6K0

    Unfortunately no generational garbage collector yet. :-(
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Sat Nov 25 13:10:18 2023
    From Newsgroup: comp.lang.prolog

    To advance the State of the Art and track performance improvements,
    some automatization would be helpful. I can test manually WASM via
    this here https://dev.swi-prolog.org/wasm/shell . Since my recent
    performance tuning of Dogelog Player for JavaScript I beat 32-bit WASM SWI-Prolog. This holds not yet for the SAT Solver test cases, that need
    GC improvements but for the core test cases. I only tested my Ryzen.
    Don’t know yet results for Yoga:
    dog swi
    nrev 1247 1223
    crypt 894 2351
    deriv 960 1415
    poly 959 1475
    sortq 1313 1825
    tictac 1587 2400
    queens 1203 2316
    query 1919 4565
    mtak 1376 1584
    perfect 1020 1369
    calc 1224 1583
    Total 13702 22106
    LoL
    Mild Shock schrieb am Samstag, 25. November 2023 um 16:23:07 UTC+1:
    How my Dogelog Player garbage collector works:

    Ashes to ashes, funk to funky
    We know Major Tom's a junkie
    Strung out in heaven's high
    Hitting an all-time low
    https://www.youtube.com/watch?v=CMThz7eQ6K0

    Unfortunately no generational garbage collector yet. :-(
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Mon Nov 27 09:31:23 2023
    From Newsgroup: comp.lang.prolog


    Scryer Prolog has made amazing leaps recently concerning
    performance, its now only like 2-3 times slower than
    SWI-Prolog! What does it prevent to get faster than SWI-Prolog?
    See for yourself. Here some testing with a very recent version.
    Interestingly tictac shows it has some problems with negation-
    as-failure and/or call/1. Maybe they should allocate more
    time to these areas instead of inference counting formatting:
    $ target/release/scryer-prolog -v
    v0.9.3-50-gb8ef3678
    nrev % CPU time: 0.304s, 3_024_548 inferences
    crypt % CPU time: 0.422s, 4_392_537 inferences
    deriv % CPU time: 0.462s, 3_150_149 inferences
    poly % CPU time: 0.394s, 3_588_369 inferences
    sortq % CPU time: 0.481s, 3_654_653 inferences
    tictac % CPU time: 1.591s, 3_285_766 inferences
    queens % CPU time: 0.517s, 5_713_596 inferences
    query % CPU time: 0.909s, 8_678_936 inferences
    mtak % CPU time: 0.425s, 6_901_822 inferences
    perfect % CPU time: 0.763s, 5_321_436 inferences
    calc % CPU time: 0.626s, 6_700_379 inferences
    true.
    Compared to SWI-Prolog on the same machine:
    $ swipl --version
    SWI-Prolog version 9.1.18 for x86_64-linux
    nrev % 2,994,497 inferences, 0.067 CPU in 0.067 seconds
    crypt % 4,166,441 inferences, 0.288 CPU in 0.287 seconds
    deriv % 2,100,068 inferences, 0.139 CPU in 0.139 seconds
    poly % 2,087,479 inferences, 0.155 CPU in 0.155 seconds
    sortq % 3,624,602 inferences, 0.173 CPU in 0.173 seconds
    tictac % 1,012,615 inferences, 0.184 CPU in 0.184 seconds
    queens % 4,596,063 inferences, 0.266 CPU in 0.266 seconds
    query % 8,639,878 inferences, 0.622 CPU in 0.622 seconds
    mtak % 3,943,818 inferences, 0.162 CPU in 0.162 seconds
    perfect % 3,241,199 inferences, 0.197 CPU in 0.197 seconds
    calc % 3,060,151 inferences, 0.180 CPU in 0.180 seconds
    Mild Shock schrieb am Samstag, 25. November 2023 um 22:10:20 UTC+1:
    To advance the State of the Art and track performance improvements,
    some automatization would be helpful. I can test manually WASM via
    this here https://dev.swi-prolog.org/wasm/shell . Since my recent

    performance tuning of Dogelog Player for JavaScript I beat 32-bit WASM SWI-Prolog. This holds not yet for the SAT Solver test cases, that need
    GC improvements but for the core test cases. I only tested my Ryzen.

    Don’t know yet results for Yoga:

    dog swi
    nrev 1247 1223
    crypt 894 2351
    deriv 960 1415
    poly 959 1475
    sortq 1313 1825
    tictac 1587 2400
    queens 1203 2316
    query 1919 4565
    mtak 1376 1584
    perfect 1020 1369
    calc 1224 1583
    Total 13702 22106

    LoL
    Mild Shock schrieb am Samstag, 25. November 2023 um 16:23:07 UTC+1:
    How my Dogelog Player garbage collector works:

    Ashes to ashes, funk to funky
    We know Major Tom's a junkie
    Strung out in heaven's high
    Hitting an all-time low
    https://www.youtube.com/watch?v=CMThz7eQ6K0

    Unfortunately no generational garbage collector yet. :-(
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Nov 28 21:47:13 2023
    From Newsgroup: comp.lang.prolog

    Testing scryer-prolog doesn’t make any sense. Its not a
    Prolog system. It has memory leaks somewhere.
    Just try my SAT solver test suite:
    ?- between(1,100,_), suite_quiet, fail; true.
    VSZ and RSS memory is going up and up, with no end.
    Clogging my machine. I don’t think that this should happen,
    that a failure driven loop eats all memory?
    Thats just a fraud. How do you set some limits?
    Mild Shock schrieb am Montag, 27. November 2023 um 18:31:25 UTC+1:
    Scryer Prolog has made amazing leaps recently concerning
    performance, its now only like 2-3 times slower than
    SWI-Prolog! What does it prevent to get faster than SWI-Prolog?

    See for yourself. Here some testing with a very recent version. Interestingly tictac shows it has some problems with negation-
    as-failure and/or call/1. Maybe they should allocate more

    time to these areas instead of inference counting formatting:

    $ target/release/scryer-prolog -v
    v0.9.3-50-gb8ef3678

    nrev % CPU time: 0.304s, 3_024_548 inferences
    crypt % CPU time: 0.422s, 4_392_537 inferences
    deriv % CPU time: 0.462s, 3_150_149 inferences
    poly % CPU time: 0.394s, 3_588_369 inferences
    sortq % CPU time: 0.481s, 3_654_653 inferences
    tictac % CPU time: 1.591s, 3_285_766 inferences
    queens % CPU time: 0.517s, 5_713_596 inferences
    query % CPU time: 0.909s, 8_678_936 inferences
    mtak % CPU time: 0.425s, 6_901_822 inferences
    perfect % CPU time: 0.763s, 5_321_436 inferences
    calc % CPU time: 0.626s, 6_700_379 inferences
    true.

    Compared to SWI-Prolog on the same machine:

    $ swipl --version
    SWI-Prolog version 9.1.18 for x86_64-linux

    nrev % 2,994,497 inferences, 0.067 CPU in 0.067 seconds
    crypt % 4,166,441 inferences, 0.288 CPU in 0.287 seconds
    deriv % 2,100,068 inferences, 0.139 CPU in 0.139 seconds
    poly % 2,087,479 inferences, 0.155 CPU in 0.155 seconds
    sortq % 3,624,602 inferences, 0.173 CPU in 0.173 seconds
    tictac % 1,012,615 inferences, 0.184 CPU in 0.184 seconds
    queens % 4,596,063 inferences, 0.266 CPU in 0.266 seconds
    query % 8,639,878 inferences, 0.622 CPU in 0.622 seconds
    mtak % 3,943,818 inferences, 0.162 CPU in 0.162 seconds
    perfect % 3,241,199 inferences, 0.197 CPU in 0.197 seconds
    calc % 3,060,151 inferences, 0.180 CPU in 0.180 seconds
    Mild Shock schrieb am Samstag, 25. November 2023 um 22:10:20 UTC+1:
    To advance the State of the Art and track performance improvements,
    some automatization would be helpful. I can test manually WASM via
    this here https://dev.swi-prolog.org/wasm/shell . Since my recent

    performance tuning of Dogelog Player for JavaScript I beat 32-bit WASM SWI-Prolog. This holds not yet for the SAT Solver test cases, that need
    GC improvements but for the core test cases. I only tested my Ryzen.

    Don’t know yet results for Yoga:

    dog swi
    nrev 1247 1223
    crypt 894 2351
    deriv 960 1415
    poly 959 1475
    sortq 1313 1825
    tictac 1587 2400
    queens 1203 2316
    query 1919 4565
    mtak 1376 1584
    perfect 1020 1369
    calc 1224 1583
    Total 13702 22106

    LoL
    Mild Shock schrieb am Samstag, 25. November 2023 um 16:23:07 UTC+1:
    How my Dogelog Player garbage collector works:

    Ashes to ashes, funk to funky
    We know Major Tom's a junkie
    Strung out in heaven's high
    Hitting an all-time low
    https://www.youtube.com/watch?v=CMThz7eQ6K0

    Unfortunately no generational garbage collector yet. :-(
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Nov 28 21:58:26 2023
    From Newsgroup: comp.lang.prolog


    With limits I get this result:
    $ ulimit -m 2000000
    $ ulimit -v 2000000
    $ target/release/scryer-prolog
    ?- ['program2.p'].
    true.
    ?- between(1,100,_), suite_quiet, fail; true.
    Segmentation fault
    Not ok! Should continue running till the end.
    Mild Shock schrieb am Mittwoch, 29. November 2023 um 06:47:15 UTC+1:
    Testing scryer-prolog doesn’t make any sense. Its not a
    Prolog system. It has memory leaks somewhere.
    Just try my SAT solver test suite:

    ?- between(1,100,_), suite_quiet, fail; true.

    VSZ and RSS memory is going up and up, with no end.
    Clogging my machine. I don’t think that this should happen,
    that a failure driven loop eats all memory?

    Thats just a fraud. How do you set some limits?
    Mild Shock schrieb am Montag, 27. November 2023 um 18:31:25 UTC+1:
    Scryer Prolog has made amazing leaps recently concerning
    performance, its now only like 2-3 times slower than
    SWI-Prolog! What does it prevent to get faster than SWI-Prolog?

    See for yourself. Here some testing with a very recent version. Interestingly tictac shows it has some problems with negation-
    as-failure and/or call/1. Maybe they should allocate more

    time to these areas instead of inference counting formatting:

    $ target/release/scryer-prolog -v
    v0.9.3-50-gb8ef3678

    nrev % CPU time: 0.304s, 3_024_548 inferences
    crypt % CPU time: 0.422s, 4_392_537 inferences
    deriv % CPU time: 0.462s, 3_150_149 inferences
    poly % CPU time: 0.394s, 3_588_369 inferences
    sortq % CPU time: 0.481s, 3_654_653 inferences
    tictac % CPU time: 1.591s, 3_285_766 inferences
    queens % CPU time: 0.517s, 5_713_596 inferences
    query % CPU time: 0.909s, 8_678_936 inferences
    mtak % CPU time: 0.425s, 6_901_822 inferences
    perfect % CPU time: 0.763s, 5_321_436 inferences
    calc % CPU time: 0.626s, 6_700_379 inferences
    true.

    Compared to SWI-Prolog on the same machine:

    $ swipl --version
    SWI-Prolog version 9.1.18 for x86_64-linux

    nrev % 2,994,497 inferences, 0.067 CPU in 0.067 seconds
    crypt % 4,166,441 inferences, 0.288 CPU in 0.287 seconds
    deriv % 2,100,068 inferences, 0.139 CPU in 0.139 seconds
    poly % 2,087,479 inferences, 0.155 CPU in 0.155 seconds
    sortq % 3,624,602 inferences, 0.173 CPU in 0.173 seconds
    tictac % 1,012,615 inferences, 0.184 CPU in 0.184 seconds
    queens % 4,596,063 inferences, 0.266 CPU in 0.266 seconds
    query % 8,639,878 inferences, 0.622 CPU in 0.622 seconds
    mtak % 3,943,818 inferences, 0.162 CPU in 0.162 seconds
    perfect % 3,241,199 inferences, 0.197 CPU in 0.197 seconds
    calc % 3,060,151 inferences, 0.180 CPU in 0.180 seconds
    Mild Shock schrieb am Samstag, 25. November 2023 um 22:10:20 UTC+1:
    To advance the State of the Art and track performance improvements,
    some automatization would be helpful. I can test manually WASM via
    this here https://dev.swi-prolog.org/wasm/shell . Since my recent

    performance tuning of Dogelog Player for JavaScript I beat 32-bit WASM SWI-Prolog. This holds not yet for the SAT Solver test cases, that need GC improvements but for the core test cases. I only tested my Ryzen.

    Don’t know yet results for Yoga:

    dog swi
    nrev 1247 1223
    crypt 894 2351
    deriv 960 1415
    poly 959 1475
    sortq 1313 1825
    tictac 1587 2400
    queens 1203 2316
    query 1919 4565
    mtak 1376 1584
    perfect 1020 1369
    calc 1224 1583
    Total 13702 22106

    LoL
    Mild Shock schrieb am Samstag, 25. November 2023 um 16:23:07 UTC+1:
    How my Dogelog Player garbage collector works:

    Ashes to ashes, funk to funky
    We know Major Tom's a junkie
    Strung out in heaven's high
    Hitting an all-time low
    https://www.youtube.com/watch?v=CMThz7eQ6K0

    Unfortunately no generational garbage collector yet. :-(
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Tue Nov 28 23:33:51 2023
    From Newsgroup: comp.lang.prolog

    How do you show Segmentation faults in a bar chart diagram?
    Here is a test with Trealla Prolog, same limit test, it completes the job. Doesn’t clog up the memory indefinitely, works just as expected:
    $ ./tpl -v
    Trealla Prolog (c) Infradig 2020-2023, v2.30.48-21-g8dfd
    $ ./tpl
    ?- ['../ciao/program2.p'].
    true.
    ?- between(1,100,_), suite_quiet, fail; true.
    true.
    ?-
    You have to wait some while, but you can use the command ps -aux to
    see that it doesn’t eat up memory. And I did the above test with the same very large ulimit -m | -v which wasn’t hit by a segmentation fault.
    Mild Shock schrieb am Mittwoch, 29. November 2023 um 06:58:28 UTC+1:
    With limits I get this result:

    $ target/release/scryer-prolog -v
    v0.9.3-57-ge8d8b09e
    $ ulimit -m 2000000
    $ ulimit -v 2000000
    $ target/release/scryer-prolog
    ?- ['program2.p'].
    true.
    ?- between(1,100,_), suite_quiet, fail; true.
    Segmentation fault

    Not ok! Should continue running till the end.
    Mild Shock schrieb am Mittwoch, 29. November 2023 um 06:47:15 UTC+1:
    Testing scryer-prolog doesn’t make any sense. Its not a
    Prolog system. It has memory leaks somewhere.
    Just try my SAT solver test suite:

    ?- between(1,100,_), suite_quiet, fail; true.

    VSZ and RSS memory is going up and up, with no end.
    Clogging my machine. I don’t think that this should happen,
    that a failure driven loop eats all memory?

    Thats just a fraud. How do you set some limits?
    Mild Shock schrieb am Montag, 27. November 2023 um 18:31:25 UTC+1:
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@bursejan@gmail.com to comp.lang.prolog on Thu Nov 30 15:43:37 2023
    From Newsgroup: comp.lang.prolog

    A new player has entered the chat (Amazon Q):
    #NLProc researcher @ AWS AI (@AmazonScience). Part-time
    machine learner & linguistics enthusiast. Previously: PhD
    @stanfordnlp, JD AI. He/him. Opinions my own.
    It is really humbling to be part of the team that
    launched Amazon Q, a flagship #AWS product that
    helps users interact with their knowledge corpus using LLMs.
    It's quite special to me personally, since it's only been
    3 years since I finished my PhD thesis on this exact topic. https://twitter.com/qi2peng2
    What does Gartner say about Business-Chatbots?
    Opening Keynote: The Next Era − We Shape AI
    AI Shapes Us l Gartner IT Symposium/Xpo https://www.youtube.com/watch?v=0s7Jw9xkSYQ
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@janburse@fastmail.fm to comp.lang.prolog on Tue Feb 27 17:03:59 2024
    From Newsgroup: comp.lang.prolog


    Terence Tao, "Machine Assisted Proof" https://www.youtube.com/watch?v=AayZuuDDKP0

    Mostowski Collapse schrieb:
    Don't buy your Pearls in Honk Kong. They are all fake.

    So what do you prefer, this Haskell monster: https://www.cs.nott.ac.uk/~pszgmh/countdown.pdf
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@janburse@fastmail.fm to comp.lang.prolog on Sat Mar 16 14:06:47 2024
    From Newsgroup: comp.lang.prolog

    I didn't make all my homework yet.
    For example just fiddling around with CLP(FD), I get:

    ?- maplist(in, Vs, [1\/3..4, 1..2\/4, 1..2\/4,
    1..3, 1..3, 1..6]), all_distinct(Vs).
    false.

    Does Scryer Prolog CLP(Z) have some explanator for that?
    What is exactly the conflict that it fails?

    Mild Shock schrieb:

    Terence Tao, "Machine Assisted Proof" https://www.youtube.com/watch?v=AayZuuDDKP0

    Mostowski Collapse schrieb:
    Don't buy your Pearls in Honk Kong. They are all fake.

    So what do you prefer, this Haskell monster:
    https://www.cs.nott.ac.uk/~pszgmh/countdown.pdf

    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@janburse@fastmail.fm to comp.lang.prolog on Sat Mar 16 14:13:50 2024
    From Newsgroup: comp.lang.prolog


    Or a more striking example, Peter Norvig's impossible
    Sudoku, which he claims took him 1439 seconds
    to show that it is unsolvable:

    /* Peter Norvig */
    problem(9, [[_,_,_,_,_,5,_,8,_],
    [_,_,_,6,_,1,_,4,3],
    [_,_,_,_,_,_,_,_,_],
    [_,1,_,5,_,_,_,_,_],
    [_,_,_,1,_,6,_,_,_],
    [3,_,_,_,_,_,_,_,5],
    [5,3,_,_,_,_,_,6,1],
    [_,_,_,_,_,_,_,_,4],
    [_,_,_,_,_,_,_,_,_]]).

    https://norvig.com/sudoku.html

    whereby SWI-Prolog with all_distinct/1 does
    it in a blink, even without labeling:

    ?- problem(9, M), time(sudoku(M)).
    % 316,054 inferences, 0.016 CPU in 0.020 seconds
    (80% CPU, 20227456 Lips)
    false.

    Pretty cool!

    Mild Shock schrieb:
    I didn't make all my homework yet.
    For example just fiddling around with CLP(FD), I get:

    ?- maplist(in, Vs, [1\/3..4, 1..2\/4, 1..2\/4,
              1..3, 1..3, 1..6]), all_distinct(Vs).
    false.

    Does Scryer Prolog CLP(Z) have some explanator for that?
    What is exactly the conflict that it fails?

    Mild Shock schrieb:

    Terence Tao, "Machine Assisted Proof"
    https://www.youtube.com/watch?v=AayZuuDDKP0

    Mostowski Collapse schrieb:
    Don't buy your Pearls in Honk Kong. They are all fake.

    So what do you prefer, this Haskell monster:
    https://www.cs.nott.ac.uk/~pszgmh/countdown.pdf


    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@janburse@fastmail.fm to comp.lang.prolog on Sun Mar 24 01:32:42 2024
    From Newsgroup: comp.lang.prolog

    Now I have the feeling there are no difficult 9x9
    Sudokus for the computer. At least not for computers
    running SWI-Prolog and using CLP(FD) with the global
    constraint all_distinct/1.

    I was fishing among the 17-clue Sudokus, and the
    hardest I could find so far was this one:

    /* Gordon Royle #3668 */
    problem(11,[[_,_,_,_,_,_,_,_,_],
    [_,_,_,_,_,_,_,1,2],
    [_,_,3,_,_,4,_,_,_],
    [_,_,_,_,_,_,_,_,3],
    [_,1,_,2,5,_,_,_,_],
    [6,_,_,_,_,_,7,_,_],
    [_,_,_,_,2,_,_,_,_],
    [_,_,7,_,_,_,4,_,_],
    [5,_,_,1,6,_,_,8,_]]).

    But SWI-Prolog still does it in around 3 seconds.
    SWI-Prolog does other 17-clue Sudokus in less than 100ms.

    Are there any 17-clue Sudokus that take more time?

    Mild Shock schrieb:

    Or a more striking example, Peter Norvig's impossible
    Sudoku, which he claims took him 1439 seconds
    to show that it is unsolvable:

    /* Peter Norvig */
    problem(9, [[_,_,_,_,_,5,_,8,_],
                [_,_,_,6,_,1,_,4,3],
                [_,_,_,_,_,_,_,_,_],
                [_,1,_,5,_,_,_,_,_],
                [_,_,_,1,_,6,_,_,_],
                [3,_,_,_,_,_,_,_,5],
                [5,3,_,_,_,_,_,6,1],
                [_,_,_,_,_,_,_,_,4],
                [_,_,_,_,_,_,_,_,_]]).

    https://norvig.com/sudoku.html

    whereby SWI-Prolog with all_distinct/1 does
    it in a blink, even without labeling:

    ?- problem(9, M), time(sudoku(M)).
    % 316,054 inferences, 0.016 CPU in 0.020 seconds
     (80% CPU, 20227456 Lips)
    false.

    Pretty cool!

    Mild Shock schrieb:
    I didn't make all my homework yet.
    For example just fiddling around with CLP(FD), I get:

    ?- maplist(in, Vs, [1\/3..4, 1..2\/4, 1..2\/4,
               1..3, 1..3, 1..6]), all_distinct(Vs).
    false.

    Does Scryer Prolog CLP(Z) have some explanator for that?
    What is exactly the conflict that it fails?

    Mild Shock schrieb:

    Terence Tao, "Machine Assisted Proof"
    https://www.youtube.com/watch?v=AayZuuDDKP0

    Mostowski Collapse schrieb:
    Don't buy your Pearls in Honk Kong. They are all fake.

    So what do you prefer, this Haskell monster:
    https://www.cs.nott.ac.uk/~pszgmh/countdown.pdf



    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mild Shock@janburse@fastmail.fm to comp.lang.prolog on Sun Mar 24 18:26:20 2024
    From Newsgroup: comp.lang.prolog

    Is 3 seconds even enough to generate
    unique Sudokus? How many trials would be
    needed? The uniqueness problem

    seems to have no useful reduction,
    already the question whether a partial
    latin square has a unique solution

    is NP complete?

    Finding Another Solution
    T. Yato & T. Seta - 2002
    https://academic.timwylie.com/17CSCI4341/sudoku.pdf

    Mild Shock schrieb:
    Now I have the feeling there are no difficult 9x9
    Sudokus for the computer. At least not for computers
    running SWI-Prolog and using CLP(FD) with the global
    constraint all_distinct/1.

    I was fishing among the 17-clue Sudokus, and the
    hardest I could find so far was this one:

    /* Gordon Royle #3668 */
    problem(11,[[_,_,_,_,_,_,_,_,_],
                [_,_,_,_,_,_,_,1,2],
                [_,_,3,_,_,4,_,_,_],
                [_,_,_,_,_,_,_,_,3],
                [_,1,_,2,5,_,_,_,_],
                [6,_,_,_,_,_,7,_,_],
                [_,_,_,_,2,_,_,_,_],
                [_,_,7,_,_,_,4,_,_],
                [5,_,_,1,6,_,_,8,_]]).

    But SWI-Prolog still does it in around 3 seconds.
    SWI-Prolog does other 17-clue Sudokus in less than 100ms.

    Are there any 17-clue Sudokus that take more time?
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Mikko@mikko.levanto@iki.fi to comp.lang.prolog on Mon Mar 25 09:59:19 2024
    From Newsgroup: comp.lang.prolog

    On 2024-03-24 17:26:20 +0000, Mild Shock said:

    https://academic.timwylie.com/17CSCI4341/sudoku.pdf

    For an expamle about what is reasonable to expect see pages
    https://mlevanto.github.io/solver.html
    https://mlevanto.github.io/SudokuV.html
    https://mlevanto.github.io/Latina.html

    The first one is a solver. It also determines whether the
    solution is unique.

    The other two problem generators. They are a bit slow but
    still usable.

    Buttons at the bottom are for saving the problem or solution
    in different file formats.
    --
    Mikko

    --- Synchronet 3.20a-Linux NewsLink 1.114