<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Wikimedia Proves Greenspun&#8217;s Tenth Law</title>
	<atom:link href="http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/feed" rel="self" type="application/rss+xml" />
	<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law</link>
	<description>Committees exist to share blame.</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:11:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Jared</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-10464</link>
		<dc:creator>Jared</dc:creator>
		<pubDate>Sun, 15 Apr 2007 05:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-10464</guid>
		<description>My main beef with TeX is that it&#039;s not consistent.

On the other hand, I&#039;m not sure whether Haskell or Scheme are expressive enough to make a comfortable definitional interpreter for a domain-specific language.

My current hope is that Haskell becomes rich enough that every document can have its own XML Schema and I throw together a few short scripts to typeset it.</description>
		<content:encoded><![CDATA[<p>My main beef with TeX is that it&#8217;s not consistent.</p>
<p>On the other hand, I&#8217;m not sure whether Haskell or Scheme are expressive enough to make a comfortable definitional interpreter for a domain-specific language.</p>
<p>My current hope is that Haskell becomes rich enough that every document can have its own XML Schema and I throw together a few short scripts to typeset it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-10462</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Sun, 15 Apr 2007 03:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-10462</guid>
		<description>I sympathise deeply with Frank. I&#039;ve strenuously avoided learning new Wiki markups but despite this I realise now that I&#039;ve had to become moderately competent in FOUR: &lt;a href=&quot;http://c2.com/&quot; rel=&quot;nofollow&quot;&gt;c2.com&lt;/a&gt; (of course), Wikipedia, &lt;a href=&quot;http://twiki.org&quot; rel=&quot;nofollow&quot;&gt;TWiki&lt;/a&gt; (still my favourite) and Trac. 

Then there are the documentation markups I&#039;ve been faced with: Doxygen and JavaDoc (inferior to Doxygen).

That is not to mention the &lt;i&gt;typesetting&lt;/i&gt; markups I&#039;ve used... from JustText to TeX (the king of them all):

&lt;i&gt;As to markup turing completeness, Iâ€™ve wondered if it might not be possible to design from the other direction - start from a programming language, say, Haskell or Scheme, implement combinators for markup that look very wiki-like, add a layer of syntactic sugar&lt;/i&gt;

I think you end up with TeX; those who forget the lessons of... yadda yadda.</description>
		<content:encoded><![CDATA[<p>I sympathise deeply with Frank. I&#8217;ve strenuously avoided learning new Wiki markups but despite this I realise now that I&#8217;ve had to become moderately competent in FOUR: <a href="http://c2.com/" rel="nofollow">c2.com</a> (of course), Wikipedia, <a href="http://twiki.org" rel="nofollow">TWiki</a> (still my favourite) and Trac. </p>
<p>Then there are the documentation markups I&#8217;ve been faced with: Doxygen and JavaDoc (inferior to Doxygen).</p>
<p>That is not to mention the <i>typesetting</i> markups I&#8217;ve used&#8230; from JustText to TeX (the king of them all):</p>
<p><i>As to markup turing completeness, Iâ€™ve wondered if it might not be possible to design from the other direction &#8211; start from a programming language, say, Haskell or Scheme, implement combinators for markup that look very wiki-like, add a layer of syntactic sugar</i></p>
<p>I think you end up with TeX; those who forget the lessons of&#8230; yadda yadda.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Irvken Experience &#187; Things I&#8217;ve noticed</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-899</link>
		<dc:creator>The Irvken Experience &#187; Things I&#8217;ve noticed</dc:creator>
		<pubDate>Sat, 02 Dec 2006 19:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-899</guid>
		<description>[...] &#8230;. and in the style I nicked off NTK. Programming languages evolving out of markup extension another small step to emergent AI? More crap from Mexico  Jamies Newtonmas present (if I had the money ). More time lapse fun. The economics of poverty seems currently fashionable, interesting new book follow up to Freakanomics, by the guy who contributed the &#8220;Economics of the Crack gang&#8221; research in that book. [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8230;. and in the style I nicked off NTK. Programming languages evolving out of markup extension another small step to emergent AI? More crap from Mexico  Jamies Newtonmas present (if I had the money ). More time lapse fun. The economics of poverty seems currently fashionable, interesting new book follow up to Freakanomics, by the guy who contributed the &#8220;Economics of the Crack gang&#8221; research in that book. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuel Simoni</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-283</link>
		<dc:creator>Manuel Simoni</dc:creator>
		<pubDate>Tue, 17 Oct 2006 13:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-283</guid>
		<description>Please, this can only be the Weak interpretation of Greenspun&#039;s Tenth. 

I&#039;m quite sure that Greenspun actually had a lot of Common Lisp&#039;s advanced features like macros, reader macros, CLOS, etc in mind when he defined his rule.</description>
		<content:encoded><![CDATA[<p>Please, this can only be the Weak interpretation of Greenspun&#8217;s Tenth. </p>
<p>I&#8217;m quite sure that Greenspun actually had a lot of Common Lisp&#8217;s advanced features like macros, reader macros, CLOS, etc in mind when he defined his rule.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: darkness</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-282</link>
		<dc:creator>darkness</dc:creator>
		<pubDate>Mon, 16 Oct 2006 20:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-282</guid>
		<description>For simple things, a wiki markup is typically much faster: typing &lt;strong&gt;foo&lt;/strong&gt; for the twentieth time gets to be hard on the fingers, compared to (in Markdown syntax) **foo**.  Also, I find reading well-designed wiki markups easier than reading HTML (see above example).

Now, as one reader commented, when you get down to doing more complex formatting tasks, a wiki should really let you revert back to HTML.</description>
		<content:encoded><![CDATA[<p>For simple things, a wiki markup is typically much faster: typing &lt;strong&gt;foo&lt;/strong&gt; for the twentieth time gets to be hard on the fingers, compared to (in Markdown syntax) **foo**.  Also, I find reading well-designed wiki markups easier than reading HTML (see above example).</p>
<p>Now, as one reader commented, when you get down to doing more complex formatting tasks, a wiki should really let you revert back to HTML.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian Morrison</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-281</link>
		<dc:creator>Julian Morrison</dc:creator>
		<pubDate>Mon, 16 Oct 2006 19:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-281</guid>
		<description>There&#039;s two main reasons for wiki text when you leave aside the spurious &quot;easier&quot;. One, HTML has no visual resemblance to its result. Wiki text always aims to get this resemblance. Two, HTML lets you waste time and play silly buggers choosing your own look-and-feel where wiki text almost forces you to play by the site&#039;s layout rules. Without it, Wikipedia would look like MySpace.

As to markup turing completeness, I&#039;ve wondered if it might not be possible to design from the other direction - start from a programming language, say, Haskell or Scheme, implement combinators for markup that look very wiki-like, add a layer of syntactic sugar (treat barewords as strings, etc). It wouldn&#039;t just be Turing complete, it would be a powerful programming language. Layout combinators could replace templates, for example.</description>
		<content:encoded><![CDATA[<p>There&#8217;s two main reasons for wiki text when you leave aside the spurious &#8220;easier&#8221;. One, HTML has no visual resemblance to its result. Wiki text always aims to get this resemblance. Two, HTML lets you waste time and play silly buggers choosing your own look-and-feel where wiki text almost forces you to play by the site&#8217;s layout rules. Without it, Wikipedia would look like MySpace.</p>
<p>As to markup turing completeness, I&#8217;ve wondered if it might not be possible to design from the other direction &#8211; start from a programming language, say, Haskell or Scheme, implement combinators for markup that look very wiki-like, add a layer of syntactic sugar (treat barewords as strings, etc). It wouldn&#8217;t just be Turing complete, it would be a powerful programming language. Layout combinators could replace templates, for example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Labnotes &#187; Rounded Corners - 46</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-280</link>
		<dc:creator>Labnotes &#187; Rounded Corners - 46</dc:creator>
		<pubDate>Mon, 16 Oct 2006 18:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-280</guid>
		<description>[...] Wikimedia Proves Greenspunâ€™s Tenth Law. How long before it proves Zawinski&#8217;s Law? [...]</description>
		<content:encoded><![CDATA[<p>[...] Wikimedia Proves Greenspunâ€™s Tenth Law. How long before it proves Zawinski&#8217;s Law? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashibaka</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-279</link>
		<dc:creator>Ashibaka</dc:creator>
		<pubDate>Mon, 16 Oct 2006 15:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-279</guid>
		<description>Wikipedia actually does let you use HTML for most things.</description>
		<content:encoded><![CDATA[<p>Wikipedia actually does let you use HTML for most things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MentalPolyphonics :: Milestone</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-138</link>
		<dc:creator>MentalPolyphonics :: Milestone</dc:creator>
		<pubDate>Fri, 08 Sep 2006 17:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-138</guid>
		<description>[...] Remember that time Jared got on BoingBoing? [...]</description>
		<content:encoded><![CDATA[<p>[...] Remember that time Jared got on BoingBoing? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dd</title>
		<link>http://mentalpolyphonics.com/posts/wikimedia-proves-greenspuns-tenth-law/comment-page-1#comment-39</link>
		<dc:creator>dd</dc:creator>
		<pubDate>Tue, 15 Aug 2006 18:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://menpofo.flanjob.com/?p=30#comment-39</guid>
		<description>This entry led me to hypothesize that small system as wikipedia and del.icio.us   emarging language had becoming Turing complete thus become full-tarm  language. and then eventually to be sufficient to be called functional language. Hence, Wikimedia and del.icio.us proves the Strong interpretation of Greenspunâ€™s Tenth Rule: any sufficiently advanced system will contain a functional (programming) language.

http://eirepreneur.blogs.com/eirepreneur/2006/03/how_social_book.html

It seems that intelligence, natural or artificial, is an emergent property of collective communication. Human con-sciousness itself may be an epiphenomenon of extraordinary processing power.</description>
		<content:encoded><![CDATA[<p>This entry led me to hypothesize that small system as wikipedia and del.icio.us   emarging language had becoming Turing complete thus become full-tarm  language. and then eventually to be sufficient to be called functional language. Hence, Wikimedia and del.icio.us proves the Strong interpretation of Greenspunâ€™s Tenth Rule: any sufficiently advanced system will contain a functional (programming) language.</p>
<p><a href="http://eirepreneur.blogs.com/eirepreneur/2006/03/how_social_book.html" rel="nofollow">http://eirepreneur.blogs.com/eirepreneur/2006/03/how_social_book.html</a></p>
<p>It seems that intelligence, natural or artificial, is an emergent property of collective communication. Human con-sciousness itself may be an epiphenomenon of extraordinary processing power.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

