Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Laya the open source version of Jev(convaiinnovations.com ↗)
    89comments
  2. A graphical desktop for the ZX Spectrum(github.com/mindbox77 ↗)
    14comments
  3. AI-generated posters don’t have to be horrible(john.hartnup.uk ↗)
    381comments
  4. Tin: full-text search for Postgres(planetscale.com ↗)
    8comments
  5. What Zig felt like, coming from Rust(besok.github.io ↗)
    59comments
  6. Human brain is two separate organs, Stanford Medicine-led research finds(stanford.edu ↗)
    169comments
  7. “The Secret Life of Circuits” is here(coredump.cx ↗)
    37comments
  8. Asking Authors About Their Own Papers(medium.com/tmlrorg ↗)
    10comments
  9. Android 17 is the first since 3.x to add new APIs without releasing to the AOSP(grapheneos.social ↗)
    523comments
  10. Black Holes or Black Hole Stars? Astronomers Spar over 'Little Red Dots'(quantamagazine.org ↗)
    7comments
  11. GPT-6 Astra Solves a WWI German Radio Cipher(prinzai.com ↗)
    121comments
  12. San Francisco Onion Futures Company(onionfutures.com ↗)
    98comments
  13. If math is more than proof, we need to better celebrate the rest of it(terrytao.wordpress.com ↗)
    176comments
  14. Learning Another Language May Be One of the Best Ways to Keep Your Brain Healthy(theconversation.com ↗)
    18comments
  15. I built the fastest PHP webserver in the world(qbixserver.com ↗)
    discuss
  16. Cloudflare Quick Tunnels(cloudflare.com ↗)
    299comments
  17. How to Write with an LLM(sockpuppet.org ↗)
    360comments
  18. Communication by means of modulated Johnson noise(pnas.org ↗)
    16comments
  19. You can run Git on object storage if you re-make packfiles(tigrisdata.com ↗)
    23comments
  20. SDCC – Small Device C Compiler(sourceforge.net ↗)
    22comments
  21. Saving another 100TB of RAM(cloudflare.com ↗)
    87comments
  22. Science Is Open Software(jepedersen.dk ↗)
    47comments
  23. Ray Ozzie and the Optimism of Being Early(reproof.app ↗)
    7comments
  24. From Stonemasons to Carpenters(thelastsoftwareengineer.substack.com ↗)
    4comments
  25. Why building a Rust LSP is hard(rust-glancer.github.io ↗)
    44comments
  26. How OpenAI Used Its Own LLMs to Design Its Jalapeño Chip(ieee.org ↗)
    115comments
  27. The first new cat species discovered in 100 years(nationalgeographic.com ↗)
    120comments
  28. Ctenophores: Wonders of Biology(quantamagazine.org ↗)
    6comments
  29. OpenJev(openjev.com ↗)
    277comments
  30. Goroutine Leak Profiles(go.dev ↗)
    6comments

Some documents on AM and EURISKO

32 pointsby 7y agoblog.funcall.org
10 comments
7y agoHN ↗

It's really basic. When I read the code I felt disappointed, though maybe someone else will feel energized to expand it.

I thought I had seen another recreation, in Bratko's book on Prolog programming for AI, but if it is there then it got dropped in the second edition. Maybe my memory got confused between that book and Tanimoto's.

7y agoHN ↗

For those unaware of the context...

I was around and actually following AI at the time. After some early success with expert systems, the field had fallen into a trough of disillusionment. Even chess was still "unsolved" in the sense that computers had barely reached master level and were still several years before they'd become truly world class (let alone dominant). The very possibility of accurate speech or image recognition was being called into question. At that time, in sharp contrast to today, AI was a specialty most ambitious people in CS were running away from.

Thus, it was a bit of a shock when Eurisko won the Traveller "Trillion Credit Squadron" tournament. Traveller was a space-themed RPG, and TCS was a very detailed space-combat outgrowth of that. That a new kind of AI (what we now know as genetic programming was far from the AI mainstream) would excel at such an open-ended task was surprising. That it would do so at such an obviously military-relevant task in what was still the Cold War was a little scary. I for one was a bit relieved when Lenat turned his and his creations' attention to more benign tasks instead of disappearing into the military-industrial complex.

Lenat, whose ideas were initially viewed with skepticism and worse, did quite possibly more than anyone else at the time to keep AI interesting and relevant. If you're working on AI/ML and don't know the story, I highly recommend digging into it.

7y agoHN ↗

This bit about EURISKO exploiting its own heuristic scoring mechanism is cute:

One of the first heuristics that EURISKO synthesized (H59) quickly attained nearly the highest Worth possible (999). Quite excitedly, we examined it and could not understand at first what it was doing that was so terrific. We monitored it carefully, and finally realized how it worked: whenever a new conjecture was made with high worth, this rule put its own name down as one of the discoverers! It turned out to be particularly difficult to prevent this generic type of finessing of EURISKO'S evaluation mechanism. Since the rules had full access to EURISKO'S code, they would have access to any safeguards we might try to implement. We finally opted for having a small 'meta-level' of protected code that the rest of the system could not modify.

7y agoHN ↗

What I find most incredible about EURISKO is it did all that on what, by today's standards, is a very small amount of computational power.

Just as outstanding is that, in all these years, in terms of open-ended problem solving, nothing has truly managed to surpass it.

The conjunction of those two things is a bit scary because it suggests to me that current methods are probably not making the most effective use of compute. What happens when that is corrected?

7y agoHN ↗

There is no credible documentation of EURISKO's achievements. No one has every actually seen EURISKO's source code except for Lenat.

Despite huge advances in technology, in computational power, and in the amount of engineers and grad students thrown at these problems, the magical reasoning feats have never been reproduced by anyone else - not even by Lenat's much more expensive project Cyc.

What's more, Lenat did not give a consistent account of the Traveler tournament. One time he claimed "ninety-six ships in Eurisko’s fleet, most of which were slow and clumsy because of their heavy armor", other times he would claim the winning strategy was "astronomical number of small ships like P.T. boats, with powerful weapons but absolutely no defense and no mobility".

The most probable explanation is that there's more myth than truth in the stories about EURISKO.

(on a less serious note, the jargon file entry for "bogosity" references Lenat; see http://itre.cis.upenn.edu/~myl/languagelog/archives/003515.h...)

7y agoHN ↗

IIRC there were two different Traveler entries in different years, and they changed the rules in between to fix the problems the first win had revealed. After the second win they said they'd cancel the tournament if he entered again.