<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Panopticon Central</title>
	<atom:link href="http://panopticoncentral.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://panopticoncentral.net</link>
	<description>a blog on programming languages and other stuff...</description>
	<lastBuildDate>Mon, 12 Mar 2012 18:28:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on The Use/Build Fallacy by mike</title>
		<link>http://panopticoncentral.net/2012/03/08/the-usebuild-fallacy/#comment-460</link>
		<dc:creator><![CDATA[mike]]></dc:creator>
		<pubDate>Mon, 12 Mar 2012 18:28:34 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/?p=41#comment-460</guid>
		<description><![CDATA[Nice. There&#039;s a relevant cite from a field that&#039;s closer to what I do as well: &quot;If the topic is physics, most people are happy to defer to physicists; if the topic is digestion, even though most people can digest food, they still defer to the gastroenterologists. But if the topic is language, everyone thinks they’re a linguist.&quot; (Ronald Kephart)]]></description>
		<content:encoded><![CDATA[<p>Nice. There&#8217;s a relevant cite from a field that&#8217;s closer to what I do as well: &#8220;If the topic is physics, most people are happy to defer to physicists; if the topic is digestion, even though most people can digest food, they still defer to the gastroenterologists. But if the topic is language, everyone thinks they’re a linguist.&#8221; (Ronald Kephart)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Use/Build Fallacy by Dan Sutton</title>
		<link>http://panopticoncentral.net/2012/03/08/the-usebuild-fallacy/#comment-458</link>
		<dc:creator><![CDATA[Dan Sutton]]></dc:creator>
		<pubDate>Mon, 12 Mar 2012 16:57:13 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/?p=41#comment-458</guid>
		<description><![CDATA[Interesting article. I tend to get around the problem of language inflexibility by writing languages which are designed to solve very specific tasks: the transfer of data from one data structure to another, for example, or the control of a certain IP-addressable device. So in a sense, I&#039;m thinking of the language more as a shorthand to allow me to put together sets of instructions quickly without having to think about coding them at a lower level in C, or whatever... the languages concerned don&#039;t need to be particularly flexible (a data transfer language doesn&#039;t need to have good graphics routines in it, for example) just as long as they can take care of the tasks at hand... but they do need to be extensible, so that I can always extend them if I need to. I think the key in designing languages is to make sure that the syntax is as extensible as you can make it, within the constraints of what you&#039;re designing the language to do... so that if you need to extend the language at some point, you can do so without having to redefine what&#039;s already there: as you say, historical decisions come back to bite you if you&#039;re not careful. This can be done by means of libraries (C, etc.) or by means of a seemingly infinitely extensible command structure (SQL, xbase, etc.) or by both; essentially, designing such a thing is more a matter of &quot;don&#039;t design something which restricts itself&quot; than &quot;design something you can expand on later&quot;, in that the former implies the latter.]]></description>
		<content:encoded><![CDATA[<p>Interesting article. I tend to get around the problem of language inflexibility by writing languages which are designed to solve very specific tasks: the transfer of data from one data structure to another, for example, or the control of a certain IP-addressable device. So in a sense, I&#8217;m thinking of the language more as a shorthand to allow me to put together sets of instructions quickly without having to think about coding them at a lower level in C, or whatever&#8230; the languages concerned don&#8217;t need to be particularly flexible (a data transfer language doesn&#8217;t need to have good graphics routines in it, for example) just as long as they can take care of the tasks at hand&#8230; but they do need to be extensible, so that I can always extend them if I need to. I think the key in designing languages is to make sure that the syntax is as extensible as you can make it, within the constraints of what you&#8217;re designing the language to do&#8230; so that if you need to extend the language at some point, you can do so without having to redefine what&#8217;s already there: as you say, historical decisions come back to bite you if you&#8217;re not careful. This can be done by means of libraries (C, etc.) or by means of a seemingly infinitely extensible command structure (SQL, xbase, etc.) or by both; essentially, designing such a thing is more a matter of &#8220;don&#8217;t design something which restricts itself&#8221; than &#8220;design something you can expand on later&#8221;, in that the former implies the latter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Use/Build Fallacy by Scott</title>
		<link>http://panopticoncentral.net/2012/03/08/the-usebuild-fallacy/#comment-444</link>
		<dc:creator><![CDATA[Scott]]></dc:creator>
		<pubDate>Thu, 08 Mar 2012 22:49:06 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/?p=41#comment-444</guid>
		<description><![CDATA[Great post.

The hypothetical &quot;Part 2&quot; of this post should remind the experts that, just because the users can&#039;t build, you can&#039;t assume that they are clueless and have no insight into what it takes to build.  Case in point: I&#039;m no doctor, but there have been a couple of occasions where I argued with a doctor until they saw my point and recommended different treatment.  In short, don&#039;t let your expertise blind you.]]></description>
		<content:encoded><![CDATA[<p>Great post.</p>
<p>The hypothetical &#8220;Part 2&#8243; of this post should remind the experts that, just because the users can&#8217;t build, you can&#8217;t assume that they are clueless and have no insight into what it takes to build.  Case in point: I&#8217;m no doctor, but there have been a couple of occasions where I argued with a doctor until they saw my point and recommended different treatment.  In short, don&#8217;t let your expertise blind you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Software patents, revisited by Sriram Krishnan</title>
		<link>http://panopticoncentral.net/2012/02/16/software-patents-revisited/#comment-381</link>
		<dc:creator><![CDATA[Sriram Krishnan]]></dc:creator>
		<pubDate>Thu, 16 Feb 2012 22:37:06 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/?p=36#comment-381</guid>
		<description><![CDATA[ex-MSFT person here. Your last paragraph resonates strongly with me since I believed the same things you wrote in your original blog post. I believe MSFT&#039;s behavior in situations like Android licensing is terrible and in breach of the social contract it made with a lot of employees. See my longer comment here http://news.ycombinator.com/item?id=3599782]]></description>
		<content:encoded><![CDATA[<p>ex-MSFT person here. Your last paragraph resonates strongly with me since I believed the same things you wrote in your original blog post. I believe MSFT&#8217;s behavior in situations like Android licensing is terrible and in breach of the social contract it made with a lot of employees. See my longer comment here <a href="http://news.ycombinator.com/item?id=3599782" rel="nofollow">http://news.ycombinator.com/item?id=3599782</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Black Hole Projects by Henry Skoglund</title>
		<link>http://panopticoncentral.net/2011/08/01/black-hole-projects/#comment-176</link>
		<dc:creator><![CDATA[Henry Skoglund]]></dc:creator>
		<pubDate>Thu, 22 Sep 2011 09:39:37 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/2011/08/01/black-hole-projects/#comment-176</guid>
		<description><![CDATA[Hi, thanks for answering. Indeed, I think for WinRT to run well on ARM it sure needs to be lean and focused
The reason I posed the question was, when you realize all the stuff that has to be implemented DirectX, DCOM, Jet Blue, registry, ARM simulator etc. it&#039;s a tall order. I guess we&#039;ll find out soon enough!]]></description>
		<content:encoded><![CDATA[<p>Hi, thanks for answering. Indeed, I think for WinRT to run well on ARM it sure needs to be lean and focused<br />
The reason I posed the question was, when you realize all the stuff that has to be implemented DirectX, DCOM, Jet Blue, registry, ARM simulator etc. it&#8217;s a tall order. I guess we&#8217;ll find out soon enough!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Black Hole Projects by paulv</title>
		<link>http://panopticoncentral.net/2011/08/01/black-hole-projects/#comment-175</link>
		<dc:creator><![CDATA[paulv]]></dc:creator>
		<pubDate>Wed, 21 Sep 2011 19:51:09 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/2011/08/01/black-hole-projects/#comment-175</guid>
		<description><![CDATA[Henry: Actually, not that I know of. I don&#039;t know a lot about WinRT since it&#039;s organizationally distant from where I sit, but it seems from the outside like it&#039;s been a pretty lean, focused effort. Which usually is the opposite of a black-hole project...]]></description>
		<content:encoded><![CDATA[<p>Henry: Actually, not that I know of. I don&#8217;t know a lot about WinRT since it&#8217;s organizationally distant from where I sit, but it seems from the outside like it&#8217;s been a pretty lean, focused effort. Which usually is the opposite of a black-hole project&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Black Hole Projects by Henry Skoglund</title>
		<link>http://panopticoncentral.net/2011/08/01/black-hole-projects/#comment-174</link>
		<dc:creator><![CDATA[Henry Skoglund]]></dc:creator>
		<pubDate>Tue, 20 Sep 2011 07:11:48 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/2011/08/01/black-hole-projects/#comment-174</guid>
		<description><![CDATA[If I may hazard a guess, you write that some blackhole projects are ongoing at the moment, is WinRT one of them?]]></description>
		<content:encoded><![CDATA[<p>If I may hazard a guess, you write that some blackhole projects are ongoing at the moment, is WinRT one of them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Black Hole Projects by Raj Chaudhuri</title>
		<link>http://panopticoncentral.net/2011/08/01/black-hole-projects/#comment-155</link>
		<dc:creator><![CDATA[Raj Chaudhuri]]></dc:creator>
		<pubDate>Tue, 02 Aug 2011 17:06:46 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/2011/08/01/black-hole-projects/#comment-155</guid>
		<description><![CDATA[I remember when this post was first put up. At the time, I had asked &quot;WinFS&quot;? I wonder what it is this time. It&#039;s about two years too late to ask &quot;Oslo&quot;. 

I&#039;m getting old.]]></description>
		<content:encoded><![CDATA[<p>I remember when this post was first put up. At the time, I had asked &#8220;WinFS&#8221;? I wonder what it is this time. It&#8217;s about two years too late to ask &#8220;Oslo&#8221;. </p>
<p>I&#8217;m getting old.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hitting the Big Red Switch by Black Hole Projects &#171; Panopticon Central</title>
		<link>http://panopticoncentral.net/2011/03/18/hitting-the-big-red-switch-2/#comment-154</link>
		<dc:creator><![CDATA[Black Hole Projects &#171; Panopticon Central]]></dc:creator>
		<pubDate>Mon, 01 Aug 2011 21:52:38 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/2011/03/18/hitting-the-big-red-switch-2/#comment-154</guid>
		<description><![CDATA[[...] so I may have reset my blog, but there were some interesting posts that probably shouldn’t disappear totally down the memory [...]]]></description>
		<content:encoded><![CDATA[<p>[...] so I may have reset my blog, but there were some interesting posts that probably shouldn’t disappear totally down the memory [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Seven Rules for Beginning Programmers by Quelles règles les programmeurs débutants devraient-ils toujours respecter ? Un développeur expérimenté livre ses 7 règles d&#8217;or &#124; Flomicro astuces &#38; outils&#8230; NTIC&#8230;</title>
		<link>http://panopticoncentral.net/2011/05/16/seven-rules-for-beginning-programmers/#comment-135</link>
		<dc:creator><![CDATA[Quelles règles les programmeurs débutants devraient-ils toujours respecter ? Un développeur expérimenté livre ses 7 règles d&#8217;or &#124; Flomicro astuces &#38; outils&#8230; NTIC&#8230;]]></dc:creator>
		<pubDate>Sat, 04 Jun 2011 17:02:47 +0000</pubDate>
		<guid isPermaLink="false">https://panopticoncentral.wordpress.com/2011/05/16/seven-rules-for-beginning-programmers/#comment-135</guid>
		<description><![CDATA[[...] : Blog Paul Vick    This entry was posted in Programmation. Bookmark the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] : Blog Paul Vick    This entry was posted in Programmation. Bookmark the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

