<?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: What programmers do (and why you should give it go)</title>
	<atom:link href="http://it.gen.nz/2009/10/01/what-programmers-do-and-why-you-should-give-it-go/feed/" rel="self" type="application/rss+xml" />
	<link>http://it.gen.nz/2009/10/01/what-programmers-do-and-why-you-should-give-it-go/</link>
	<description>Writings on technology and society from Wellington, New Zealand</description>
	<lastBuildDate>Thu, 29 Jul 2010 23:10: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: Adam Shand</title>
		<link>http://it.gen.nz/2009/10/01/what-programmers-do-and-why-you-should-give-it-go/comment-page-1/#comment-7768</link>
		<dc:creator>Adam Shand</dc:creator>
		<pubDate>Thu, 01 Oct 2009 11:17:41 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=793#comment-7768</guid>
		<description>Re. Weta and Python, the above is not quite acurate. The pipeline for both Rings and Kong were primarily Perl based. Python didn&#039;t get a major foothold until after Kong when Autodesk embedded Python into Maya as it&#039;s scripting language (to replace the aging Mel).   These days Python has become the defacto pipeline language for many VFX houses. .</description>
		<content:encoded><![CDATA[<p>Re. Weta and Python, the above is not quite acurate. The pipeline for both Rings and Kong were primarily Perl based. Python didn&#8217;t get a major foothold until after Kong when Autodesk embedded Python into Maya as it&#8217;s scripting language (to replace the aging Mel).   These days Python has become the defacto pipeline language for many VFX houses. .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence D'Oliveiro</title>
		<link>http://it.gen.nz/2009/10/01/what-programmers-do-and-why-you-should-give-it-go/comment-page-1/#comment-7742</link>
		<dc:creator>Lawrence D'Oliveiro</dc:creator>
		<pubDate>Wed, 30 Sep 2009 23:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=793#comment-7742</guid>
		<description>Oh, by the way, it’s “CO-BOL”, not “COB-OL”.</description>
		<content:encoded><![CDATA[<p>Oh, by the way, it’s “CO-BOL”, not “COB-OL”.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence D'Oliveiro</title>
		<link>http://it.gen.nz/2009/10/01/what-programmers-do-and-why-you-should-give-it-go/comment-page-1/#comment-7741</link>
		<dc:creator>Lawrence D'Oliveiro</dc:creator>
		<pubDate>Wed, 30 Sep 2009 22:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=793#comment-7741</guid>
		<description>Regarding programming/scripting languages based on human languages other than English, one example I can vouch for is the first version of Apple’s AppleScript scripting system for the Mac, from 1993. That had the concept of “dialects”, which were different syntaxes for the human-readable source form, all of which would compile to the same tokenized form. Besides the English “dialect”, there were also Japanese and Italian versions released, as I recall. There were even plans to make the “dialect” API public, so third parties could develop their own.

Unfortunately, it didn’t turn out to be so clean as that. Before long, the whole “dialect” concept was abandoned, and from version 1.1 onwards, AppleScript became English-only.</description>
		<content:encoded><![CDATA[<p>Regarding programming/scripting languages based on human languages other than English, one example I can vouch for is the first version of Apple’s AppleScript scripting system for the Mac, from 1993. That had the concept of “dialects”, which were different syntaxes for the human-readable source form, all of which would compile to the same tokenized form. Besides the English “dialect”, there were also Japanese and Italian versions released, as I recall. There were even plans to make the “dialect” API public, so third parties could develop their own.</p>
<p>Unfortunately, it didn’t turn out to be so clean as that. Before long, the whole “dialect” concept was abandoned, and from version 1.1 onwards, AppleScript became English-only.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
