throwaway2380
I have no complaints about the book, but I've been struggling to figure out an easy setup for "Prolog as a web app backend." Typical Prolog implementations are not designed to be used as concurrently-accessed databases. Datalog seems to be a nearby technology that is more pointed towards that use case, but even then, there seem to be scant few implementations of Datalog databases with transaction support, and near zero that are open source.
RDF/OWL databases seem to be another conceptually-near possibility, but they also seem to have few implementations that are prepared for high-scale concurrent access.
Overall, it seems that there is a decent amount of interest in "logic-type" query languages as a curiosity, but little attention to implementations that support use in OLTP business applications, which makes adoption difficult.
Does anybody have any advice?
I relate so much it hurts. The industry at large seems unable to see the lost opportunity of significant investment in technical documentation.
Whether it be something like Tor, or something like a distributed database, internet communication may require hardware and physical location of data, but there are ways to allow information transmission without being strongly reliant on a fixed physical source.
Also, this capability is not limited to the internet.
I find this phenomenon so difficult to understand.