<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Why It's Nice to be Quoted: Quasiquoting for Prolog · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1308.3941/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1308.3941/feed.xml" rel="self" type="application/rss+xml" /><item><title>Why It's Nice to be Quoted: Quasiquoting for Prolog — mentioned by zmonx</title><link>https://news.ycombinator.com/item?id=14447313</link><guid isPermaLink="false">urn:hackerpapers:mention:1308.3941:14447313</guid><pubDate>Tue, 30 May 2017 18:25:17 GMT</pubDate><description>&lt;p&gt;Thank you for your explanation! I do not in the least dispute that the goal of PHP was to help people, or that people managed to build web sites for the intended use cases. In fact, if one of PHP&amp;#x27;s goals was to allow a great number of unintended security flaws in user programs, then this was also splendidly achieved. Personally, I only cannot bring myself to call a site with security flaws &amp;quot;working&amp;quot;, and when using PHP, these flaws are simply more easily made than with Prolog in my experience. Note that I need not even go as far as making any statements about particular implementations of…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1308.3941/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
