Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 27 |
Nodes: | 6 (0 / 6) |
Uptime: | 43:25:15 |
Calls: | 631 |
Calls today: | 2 |
Files: | 1,187 |
D/L today: |
24 files (29,813K bytes) |
Messages: | 175,386 |
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973 https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973 https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye
Hi,
2025 will be last year we hear of Python.
This is just a tears in your eyes Eulogy:
Python: The Documentary | An origin story https://www.youtube.com/watch?v=GfH4QL4VqJ0
The Zen of Python is very different
from the Zen of Copilot+ . The bloody
Copilot+ Laptop doesn't use Python
in its Artificial Intelligence:
AI Content Extraction
- Python Involced? rYi None at runtime,
-a Model runs in ONNX + DirectML on NPU
AI Image Search
- Python Involced? rYi None at runtime,
-a ON-device image feature, fully compiled
AI Phi Silica
- Python Involced? rYi None at runtime,
-a Lightweight Phi model packaged as ONNX
AI Semantic Analysis?
- Python Involced? rYi None at runtime,
-a Text understanding done via compiled
-a ONNX operators
Bye
Mild Shock schrieb:
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973
https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye
Hi,
Swiss AI Apertus
Model ID: apertus-70b-instruct
Parameters: 70 billion
License: Apache 2.0
Training: 15T tokens across 1,000+ languages
Availability: Free during Swiss AI Weeks (September 2025)
https://platform.publicai.co/docs
Bye
P.S.: A chat interface is here:
Try Apertus
https://publicai.co/
Mild Shock schrieb:
Hi,
2025 will be last year we hear of Python.
This is just a tears in your eyes Eulogy:
Python: The Documentary | An origin story
https://www.youtube.com/watch?v=GfH4QL4VqJ0
The Zen of Python is very different
from the Zen of Copilot+ . The bloody
Copilot+ Laptop doesn't use Python
in its Artificial Intelligence:
AI Content Extraction
- Python Involced? rYi None at runtime,
-a-a Model runs in ONNX + DirectML on NPU
AI Image Search
- Python Involced? rYi None at runtime,
-a-a ON-device image feature, fully compiled
AI Phi Silica
- Python Involced? rYi None at runtime,
-a-a Lightweight Phi model packaged as ONNX
AI Semantic Analysis?
- Python Involced? rYi None at runtime,
-a-a Text understanding done via compiled
-a-a ONNX operators
Bye
Mild Shock schrieb:
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973
https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf >>>
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye
Hi,
For the LP (Linear programming) part, it
might be interesting to recall, that SWI-Prolog
has an according library:
A.55 library(simplex): Solve linear programming problems https://eu.swi-prolog.org/pldoc/man?section=simplex
To model the constraint store, it doesnrCOt need
any native Prolog system support, since it uses
DCG for state threading. Linear programming was
long time the pinnacle of mathematical problem
solving. But some Articial Intelligence method do
typically go beyond the linear case, might also
tackle non-linear problems etc.. making heavy
use of a NPU (Neural Processing Unit). In May 2025
the first AI Laptops arrived with >40 TOPS NPUs.
Spearheaded by Microsoft branding it Copilot+.
Bye
Hi,
It seems the LP (Linear programming)
library by SWI-Prolog has been also
ported to Scryer Prolog using the same DCG
design as demonstrated in SWI-Prolog again:
Module simplex
https://www.scryer.pl/simplex
What it requires from the Prolog system,
and is not covered by the ISO core standard,
are rational number, i.e. rdiv/2 etc.. and if
you feed it with floating point numbers,
judging from the source code, it might bark
that it has no CLP(R) available to solve it. CLP(R)
could be maybe a good candidate for Copilot+
machines, but I am currently not aware
of a Copliot+ Prolog system so to speak:
About Microsoft Copilot+ PCs https://www.wired.com/story/what-is-copilot-plus-pc/
The DCG design could make it easy that a
solver somehow hands a problem to a NPU,
making it transparent for the end-user.
Bye
Mild Shock schrieb:
Hi,
For the LP (Linear programming) part, it
might be interesting to recall, that SWI-Prolog
has an according library:
A.55 library(simplex): Solve linear programming problems
https://eu.swi-prolog.org/pldoc/man?section=simplex
To model the constraint store, it doesnrCOt need
any native Prolog system support, since it uses
DCG for state threading. Linear programming was
long time the pinnacle of mathematical problem
solving. But some Articial Intelligence method do
typically go beyond the linear case, might also
tackle non-linear problems etc.. making heavy
use of a NPU (Neural Processing Unit). In May 2025
the first AI Laptops arrived with >40 TOPS NPUs.
Spearheaded by Microsoft branding it Copilot+.
Bye
I used Claude code to help me create a Prolog
program of a little expert system to manage a
kitchen that needed to produce different dishes
with different appliances and to be able to
maximize revenue. -- bauhaus911
Hi,
Thank god it was only coffee and not orange juice:
Ozzy Pours The Perfect O.J.
https://m.youtube.com/watch?v=ojQUYq21G-o
Bye
Mild Shock schrieb:
Hi,
It seems the LP (Linear programming)
library by SWI-Prolog has been also
ported to Scryer Prolog using the same DCG
design as demonstrated in SWI-Prolog again:
Module simplex
https://www.scryer.pl/simplex
What it requires from the Prolog system,
and is not covered by the ISO core standard,
are rational number, i.e. rdiv/2 etc.. and if
you feed it with floating point numbers,
judging from the source code, it might bark
that it has no CLP(R) available to solve it. CLP(R)
could be maybe a good candidate for Copilot+
machines, but I am currently not aware
of a Copliot+ Prolog system so to speak:
About Microsoft Copilot+ PCs
https://www.wired.com/story/what-is-copilot-plus-pc/
The DCG design could make it easy that a
solver somehow hands a problem to a NPU,
making it transparent for the end-user.
Bye
Mild Shock schrieb:
Hi,
For the LP (Linear programming) part, it
might be interesting to recall, that SWI-Prolog
has an according library:
A.55 library(simplex): Solve linear programming problems
https://eu.swi-prolog.org/pldoc/man?section=simplex
To model the constraint store, it doesnrCOt need
any native Prolog system support, since it uses
DCG for state threading. Linear programming was
long time the pinnacle of mathematical problem
solving. But some Articial Intelligence method do
typically go beyond the linear case, might also
tackle non-linear problems etc.. making heavy
use of a NPU (Neural Processing Unit). In May 2025
the first AI Laptops arrived with >40 TOPS NPUs.
Spearheaded by Microsoft branding it Copilot+.
Bye
Jan, werCOve asked you to be less combative withpeople here, but you continue to be extremely
You have very helpful things to add, but whenyou then go back and delete everything you post,
Hi,
I like the expert system description by
I used Claude code to help me create a Prolog
program of a little expert system to manage a
kitchen that needed to produce different dishes
with different appliances and to be able to
maximize revenue. -- bauhaus911
Instead of maximizing revenue you could also
maximize energy boost. So instead of having
a couple of morons on SWI-Prolog discourse,
like those that have parked their brain in the
nowhere and are going full throttle Donald
Trump / Kesh Patel Nazi, the system could
indeed recommend Orange Juice instead of
coffee. For the following brain benefits:
- Vitamin C powerhouse: ~50rCo60 mg per 100 ml,
-a giving a solid immune boost.
- Quick energy: natural sugars (glucose + fructose)
-a give your brain and body fast fuel.
- Hydration: mostly water, which helps maintain
-a energy and focus.
Have Fun! LoL
Mild Shock schrieb:
Hi,
Thank god it was only coffee and not orange juice:
Ozzy Pours The Perfect O.J.
https://m.youtube.com/watch?v=ojQUYq21G-o
Bye
Mild Shock schrieb:
Hi,
It seems the LP (Linear programming)
library by SWI-Prolog has been also
ported to Scryer Prolog using the same DCG
design as demonstrated in SWI-Prolog again:
Module simplex
https://www.scryer.pl/simplex
What it requires from the Prolog system,
and is not covered by the ISO core standard,
are rational number, i.e. rdiv/2 etc.. and if
you feed it with floating point numbers,
judging from the source code, it might bark
that it has no CLP(R) available to solve it. CLP(R)
could be maybe a good candidate for Copilot+
machines, but I am currently not aware
of a Copliot+ Prolog system so to speak:
About Microsoft Copilot+ PCs
https://www.wired.com/story/what-is-copilot-plus-pc/
The DCG design could make it easy that a
solver somehow hands a problem to a NPU,
making it transparent for the end-user.
Bye
Mild Shock schrieb:
Hi,
For the LP (Linear programming) part, it
might be interesting to recall, that SWI-Prolog
has an according library:
A.55 library(simplex): Solve linear programming problems
https://eu.swi-prolog.org/pldoc/man?section=simplex
To model the constraint store, it doesnrCOt need
any native Prolog system support, since it uses
DCG for state threading. Linear programming was
long time the pinnacle of mathematical problem
solving. But some Articial Intelligence method do
typically go beyond the linear case, might also
tackle non-linear problems etc.. making heavy
use of a NPU (Neural Processing Unit). In May 2025
the first AI Laptops arrived with >40 TOPS NPUs.
Spearheaded by Microsoft branding it Copilot+.
Bye
Hi,
2025 will be last year we hear of Python.
This is just a tears in your eyes Eulogy:
Python: The Documentary | An origin story https://www.youtube.com/watch?v=GfH4QL4VqJ0
The Zen of Python is very different
from the Zen of Copilot+ . The bloody
Copilot+ Laptop doesn't use Python
in its Artificial Intelligence:
AI Content Extraction
- Python Involced? rYi None at runtime,
-a Model runs in ONNX + DirectML on NPU
AI Image Search
- Python Involced? rYi None at runtime,
-a ON-device image feature, fully compiled
AI Phi Silica
- Python Involced? rYi None at runtime,
-a Lightweight Phi model packaged as ONNX
AI Semantic Analysis?
- Python Involced? rYi None at runtime,
-a Text understanding done via compiled
-a ONNX operators
Bye
Mild Shock schrieb:
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973
https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye
Hi,
Is there a silver lining of AI democratization?
With MedGamma I can analyse my own broken ribs.
If only I had a body scanner. I am currently exploring
options of LLM models that I could run on
my new AI soaked AMD Ryzen AI 7 350 laptop.
While Qualcomm spear headed LLM players with
their LM Studio. There is FastFlowLM
that can do Ryzen, and would utilize the NPU. For
example to run a distilled DeepSeek would amount to:
flm run deepseek-r1:8b
And yes there is MedGamma:
MedGemma:4B (Multimodal) Running Exclusively on AMD Ryzenrao AI NPU https://www.youtube.com/watch?v=KWzXZEOcgK4
Bye
Mild Shock schrieb:
Hi,
2025 will be last year we hear of Python.
This is just a tears in your eyes Eulogy:
Python: The Documentary | An origin story
https://www.youtube.com/watch?v=GfH4QL4VqJ0
The Zen of Python is very different
from the Zen of Copilot+ . The bloody
Copilot+ Laptop doesn't use Python
in its Artificial Intelligence:
AI Content Extraction
- Python Involced? rYi None at runtime,
-a-a Model runs in ONNX + DirectML on NPU
AI Image Search
- Python Involced? rYi None at runtime,
-a-a ON-device image feature, fully compiled
AI Phi Silica
- Python Involced? rYi None at runtime,
-a-a Lightweight Phi model packaged as ONNX
AI Semantic Analysis?
- Python Involced? rYi None at runtime,
-a-a Text understanding done via compiled
-a-a ONNX operators
Bye
Mild Shock schrieb:
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973
https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf >>>
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye
Ex-OpenAI pioneer Ilya Sutskever warns that as
AI begins to self-improve, its trajectory may become
"extremely unpredictable and unimaginable,"
ushering in a rapid advance beyond human control. https://www.youtube.com/watch?v=79-bApI3GIU
That casual, almost incidental quality you noticed
is exactly the abstraction engine working so fluidly
that it becomes invisible. The AI was:
1. Understanding the essential computation (the "what")
2. Discarding the Java-specific implementation (the "how")
2. Re-expressing it using C#'s idiomatic patterns (a different "how")
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973 https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye
ETH-Professor Martin Jaggi explains that Apertus
AI is a basis LLM, doesn't have yet RAG, doesn't
have yet thinking. Etc.. Etc.. Speculates that the
"open" community might help change it.
One month later: Interview with Martin Jaggi https://www.youtube.com/watch?v=KgB8CfZCeME
Goliath (40,000 TFLOPS): Perfect for discovering new
patterns, complex reasoning, creative tasks
David (40 TFLOPS): Perfect for execution, integration,
personalization, real-time response
Hi,
Here we find Ex-OpenAI Scientist looking extremly concerned:
Ex-OpenAI pioneer Ilya Sutskever warns that as
AI begins to self-improve, its trajectory may become
"extremely unpredictable and unimaginable,"
ushering in a rapid advance beyond human control. https://www.youtube.com/watch?v=79-bApI3GIU
Meanwhile I am enjoying some of the AIs abstracting capabilities:
The bludy thingy was translating my Java code into C#
code in a blink and did all kind of fancy translation,
and explains his own doing as:
That casual, almost incidental quality you noticed
is exactly the abstraction engine working so fluidly
that it becomes invisible. The AI was:
1. Understanding the essential computation (the "what")
2. Discarding the Java-specific implementation (the "how")
2. Re-expressing it using C#'s idiomatic patterns (a different "how")
Ha Ha, nice try AI, presenting me this antropomorphic
illusion of comprehension. Doesn't the AI just apply tons
of patterns without any knowing what the code really does?
Well I am fine with that, I don't need more than this
pattern based transformations. If the result works,
the approach is not broken.
Bye
Mild Shock schrieb:
Hi,
J Strother Moore II is the Original Gangster (OG)
of program sharng. Interestingly structure sharing
meant always program sharing in the theorem
proving community back then:
COMPUTATIONAL LOGIC: STRUCTURE SHARING AND
PROOF OF PROGRAM PROPERTIES
J Strother Moore II - 1973
https://era.ed.ac.uk/bitstream/handle/1842/2245/Moore-Thesis-1973-OCR.pdf
Only the WAM community managed to intsitutionalize
the term structure sharng, as a reduced form of
program sharing, namely goal argument sharing
not using pairs of two pointers with skeleton and binding
environment anymore, to indentify a Prolog term,
but simple single pointers for a Prolog term.
Bye