3 ms·
An interesting aspect is that some of Prolog's ideas, such as the signature one of backwards-chaining, unification-based queries, are starting to resurface in o
by _delirium 15y ago
An interesting aspect is that some of Prolog's ideas, such as the signature one of backwards-chaining, unification-based queries, are starting to resurface in other languages, so it might be worth learning even if you don't plan to use Prolog itself.
I wrote an opinion piece a while ago about why Prolog had fallen out of favor (http://www.kmjn.org/notes/prolog_lost_steam.html http://www.kmjn.org/notes/prolog_lost_steam.html), and one of the reasons was that other declarative programming approaches, like forward-chaining, SQL w/ recursive queries, and LINQ-style dataflow variables, have bitten off a simpler but useful subset of what it bought you. In response, Mark Proctor from Drools argued that they're well on their way to importing nearly everything important from Prolog, rather than only a useful subset, including backwards chaining with unification: http://blog.athico.com/2011/04/backward-chaining-emerges-in-drools.html http://blog.athico.com/2011/04/backward-chaining-emerges-in-...
This includes a very interesting mashup of the two ideas, "reactive derivation", which does Prolog-style queries, but where the results, like with truth-maintenance systems or SQL "views", update in real time when the underlying data changes: http://blog.athico.com/2011/06/truth-maintenance-over-directed-graphs.html http://blog.athico.com/2011/06/truth-maintenance-over-direct...
Imo, the simultaneous use of Prolog-style derivation and real-time forward-chaining style truth maintenance is both really interesting and a bit mind-bending, so learning Prolog first might be a good foundation.
- andrewcooke 15y agocan you point me to something that discusses dataflow style variables in linq? (i don't use ms software and had missed this). thanks.