News for hackers. Stuff that matters.
Re:Logic Production Systems: A new mixed logic/imperative pr... by PaulHoule on Monday March 27, 2017 @11:05AM (#13968286)
Today we have production rules systems such as iLog and Drools which are head and shoulders better than OPS5 and other "expert system shells" from the golden age of A.I.

These are in widespread use for a few applications. Probably every bank has at least one iLog instance running for enforcing business rules. Another one is "complex event processing", where a RETE engine makes it easy to aggregate small events into larger events. Also, a few efforts, such as Inform7 and Clara have tried to push the boundaries of programming for non-experts and real-life applications.

It is interesting, however, that the technology is not further applied, and a deep analysis of that could be worthwhile. For instance, RETE networks can eat "callback hell" situations for lunch, much like the complex event processing case. Instead, however, we are seeing one awful Javascript framework after another, and coroutines pushed as a very narrow answer to the problems on the server.

Note that all forms of A.I. have ties to optimization. For instance, usually when you train a neural net you are minimizing some kind of an error function. Drools (and iLog) both have optimization frameworks, etc.

The recent discussion of "superintelligence" has been marked by both a lack of imagination and any awareness of previous work on the subject. For instance, Rules engines are a fairly direct answer to "AI Safety" and "AI Ethics" problems that there is so much handwringing about. Most areas that require computers to be "creative" amount to some kind of multi-objective optimization, and even if rules can't make a system good, they can at least prevent the worst abuses.

Re:Logic Production Systems: A new mixed logic/imperative pr... by saosebastiao on Monday March 27, 2017 @11:32AM (#13968547)
I'm in complete agreement. I didn't mean to give off the idea that you couldn't use Expert Systems anymore, merely that the research and publishing interest died. Implementations have definitely improved. Supposedly, Charles Forgy has continued researching and implementing improvements to his original RETE algorithm, but both the research and implementations are entirely proprietary and mostly inaccessible.

I likewise find it sad that the idea has died so much that we continue to build square wheels that were made obsolete by rule engines. I remember a futile attempt at Amazon to get a team to scrap their system in favor of a RETE based rule engine. Theirs was a poorly performing and fragile homemade "rule engine" that compiled xml rules into if/else statements, which after tens of thousands of rules had slowed to a snails pace. Somehow the magic of O(1) escaped them, and they practically required me to reimplement their system from scratch in order to convince them. So I let it go.

I had never considered the possibility of killing callback hell with a rules engine but I can definitely see it now. I personally have toyed with building a compiler that eschews the pipeline architecture with a rules engine where both analyses and optimizations are implemented as rules. I definitely think there is a world of possibilities out there, but maybe we'll need another AI winter before people consider them again.

Re:Logic Production Systems: A new mixed logic/imperative pr... by PaulHoule on Monday March 27, 2017 @11:53AM (#13968730)
+1 for the rules-driven compiler, it's one of those things that could put programming language innovation into many more hands.
Re:Logic Production Systems: A new mixed logic/imperative pr... by trapperkeeper79 on Tuesday March 28, 2017 @10:44AM (#13976960)
Getting RETE right isn't trivial. I tried looking into the fundamentals a few months ago, and was very unsatisfied - it felt like people explaining it knew parts of it but not the whole thing. I guess it is good that we have some open source implementations that can be reverse engineered by someone motivated enough.