One related workplace anecdote that a former fellow student told me: He was working on a rule-based medical recommender system, and he recognized that Prolog was an excellent fit for this project. When he first suggested that the team switch to Prolog, they were very skeptical. But someone high up in the chain was a great fan of Prolog and approved this suggestion. A few weeks later, they had completed the implementation, and the Prolog-based solution was running. My colleague told me that, a few months after that, the whole team regarded Prolog as the only viable solution to all further projects from then on!
Hm, there is such a thing as the right tool for the job. If all their jobs were very similar that makes sense, otherwise, not so much.
Are you aware of the fact that inside every Windows NT installation there was a Prolog engine to help with network configuration?
http://web.archive.org/web/20040603192757/research.microsoft...
Thank you for the link to the Prolog-based network configuration!
And what kind of reaction are you getting? As I just wrote elsewhere, I don't think this is useful for complete Prolog beginners to learn the language or even get a feel for it. Has anyone you sent this to come back with "that's neat, I read the first N chapters and have just written my first Prolog program on my own"?
What are strong cases to use Prolog/Haskell these days? :D
ebony and ivory / live together in perfect harmony
etc