<?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: Pygeon: a new educational programming language</title>
	<atom:link href="http://brianwill.net/blog/2007/01/14/pygeon-a-new-educational-programming-language/feed/" rel="self" type="application/rss+xml" />
	<link>http://brianwill.net/blog/2007/01/14/pygeon-a-new-educational-programming-language/</link>
	<description></description>
	<lastBuildDate>Thu, 25 Mar 2010 06:32:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BrianWill.net &#187; Blog Archive &#187; Syntax does/doesn&#8217;t matter</title>
		<link>http://brianwill.net/blog/2007/01/14/pygeon-a-new-educational-programming-language/comment-page-1/#comment-463</link>
		<dc:creator>BrianWill.net &#187; Blog Archive &#187; Syntax does/doesn&#8217;t matter</dc:creator>
		<pubDate>Wed, 31 Jan 2007 15:35:42 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/2007/01/14/pygeon-a-new-educational-programming-language/#comment-463</guid>
		<description>[...] My main purpose in proposing a new educational programming language is to give learners a language that expresses the core features common to modern languages in the syntactically most direct and obvious way possible. So for instance, abbreviations that are non-obvious to a programmer must be excised from the language, including the libraries, e.g. the language can&#8217;t have anything like C&#8217;s &#8220;stdio&#8221; (&#8221;standard input/output&#8221;) or &#8220;sprintf&#8221; (&#8221;string print formatted&#8221;). (Such abbreviations would be more forgivable if full-names were given in learning materials, but out of the dozens of tutorials and references of the C language I have read, only a couple do so.) Taken individually, shortcuts like these may seem like small hurdles to the initiated, but only because the initiated can no longer see how non-obvious such shortcuts are. The small hurdles quickly add up. Every quirk, every historical legacy, every shortcut is one more thing which at some point is going to cause the learner frustration, possibly halting their progress. [...]</description>
		<content:encoded><![CDATA[<p>[...] My main purpose in proposing a new educational programming language is to give learners a language that expresses the core features common to modern languages in the syntactically most direct and obvious way possible. So for instance, abbreviations that are non-obvious to a programmer must be excised from the language, including the libraries, e.g. the language can&#8217;t have anything like C&#8217;s &#8220;stdio&#8221; (&#8221;standard input/output&#8221;) or &#8220;sprintf&#8221; (&#8221;string print formatted&#8221;). (Such abbreviations would be more forgivable if full-names were given in learning materials, but out of the dozens of tutorials and references of the C language I have read, only a couple do so.) Taken individually, shortcuts like these may seem like small hurdles to the initiated, but only because the initiated can no longer see how non-obvious such shortcuts are. The small hurdles quickly add up. Every quirk, every historical legacy, every shortcut is one more thing which at some point is going to cause the learner frustration, possibly halting their progress. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
