<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: Why Your Programming Language Is &#8220;Too Academic&#8221;</title>
	<atom:link href="http://enfranchisedmind.com/blog/posts/too-academic-languages/feed/" rel="self" type="application/rss+xml" />
	<link>http://enfranchisedmind.com/blog/posts/too-academic-languages/</link>
	<description>programming, politics, &#38; other religious issues</description>
	<lastBuildDate>Fri, 12 Mar 2010 09:19:33 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Graeme Defty</title>
		<link>http://enfranchisedmind.com/blog/posts/too-academic-languages/#comment-36880</link>
		<dc:creator>Graeme Defty</dc:creator>
		<pubDate>Mon, 28 Sep 2009 11:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=1079#comment-36880</guid>
		<description>I was interested that the idea of &quot;too academic&quot; seemed hard to pin down. Intuitively I feel I know what it means (to me anyway) but would also have a tough time describing it. &quot;too wierd&quot; doesn&#039;t really help.  &quot;too hard&quot;  is part of it, but it feels more like a symptom than a cause. &quot;too powerful&quot; certainly doesn&#039;t do it.

Is it just that the language is too far in language-space from what you are familiar with? That there are too many new paradigms involved for comfort? That may be why the ability to &quot;write COBOL&quot; in your new language is such a soother. It lets you play in the language and learn the new idioms as you do so.

I still don&#039;t have a decent replacement for &quot;too academic&quot; though :-(

One other thought (which could help prove or disprove the above) is that it would be interesting to hear from someone who learned programming with a functional language about their experiences moving to Java for the first time (&quot;What do you mean, I have to tell it what to do?!&quot;) I suspect that the dificulty would be vastly reduced because that form of imperative instruction is how we tend to deal with each other. Instructions stating how to make a cup of tea are much more likely to look like C than Haskell (well, maybe not C, but you get the point ;-) )</description>
		<content:encoded><![CDATA[<p>I was interested that the idea of &#8220;too academic&#8221; seemed hard to pin down. Intuitively I feel I know what it means (to me anyway) but would also have a tough time describing it. &#8220;too wierd&#8221; doesn&#8217;t really help.  &#8220;too hard&#8221;  is part of it, but it feels more like a symptom than a cause. &#8220;too powerful&#8221; certainly doesn&#8217;t do it.</p>
<p>Is it just that the language is too far in language-space from what you are familiar with? That there are too many new paradigms involved for comfort? That may be why the ability to &#8220;write COBOL&#8221; in your new language is such a soother. It lets you play in the language and learn the new idioms as you do so.</p>
<p>I still don&#8217;t have a decent replacement for &#8220;too academic&#8221; though :-(</p>
<p>One other thought (which could help prove or disprove the above) is that it would be interesting to hear from someone who learned programming with a functional language about their experiences moving to Java for the first time (&#8220;What do you mean, I have to tell it what to do?!&#8221;) I suspect that the dificulty would be vastly reduced because that form of imperative instruction is how we tend to deal with each other. Instructions stating how to make a cup of tea are much more likely to look like C than Haskell (well, maybe not C, but you get the point ;-) )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hydrocon Session Log, 1241655767 &#171; I Built His Cage</title>
		<link>http://enfranchisedmind.com/blog/posts/too-academic-languages/#comment-34689</link>
		<dc:creator>Hydrocon Session Log, 1241655767 &#171; I Built His Cage</dc:creator>
		<pubDate>Thu, 07 May 2009 00:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=1079#comment-34689</guid>
		<description>[...] mean, what the hell? We started out functional programming by learning Scheme, another &#8220;academic&#8221; language, and I think that gave me a solid idea of what ideas like closures and currying are about. We [...]</description>
		<content:encoded><![CDATA[<p>[...] mean, what the hell? We started out functional programming by learning Scheme, another &#8220;academic&#8221; language, and I think that gave me a solid idea of what ideas like closures and currying are about. We [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Helltime for April 20 &#171; I Built His Cage</title>
		<link>http://enfranchisedmind.com/blog/posts/too-academic-languages/#comment-34454</link>
		<dc:creator>Helltime for April 20 &#171; I Built His Cage</dc:creator>
		<pubDate>Tue, 21 Apr 2009 02:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=1079#comment-34454</guid>
		<description>[...] at Enfranchised Mind, Robert Fischer refreshingly explains why languages get categorized as merely for the wizards of academia. First, I found it ironic that Robert credits Java&#8217;s popularity, somewhat backhandedly, to [...]</description>
		<content:encoded><![CDATA[<p>[...] at Enfranchised Mind, Robert Fischer refreshingly explains why languages get categorized as merely for the wizards of academia. First, I found it ironic that Robert credits Java&#8217;s popularity, somewhat backhandedly, to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Fischer</title>
		<link>http://enfranchisedmind.com/blog/posts/too-academic-languages/#comment-34452</link>
		<dc:creator>Robert Fischer</dc:creator>
		<pubDate>Mon, 20 Apr 2009 14:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=1079#comment-34452</guid>
		<description>@Tracy

In saying we should be sensitive to the limits of gradual adoption, I&#039;m talking about building hand-holding into language infrastructure based on the assumption that someone knows a mainstream language but is learning yours.  Useful compiler/runtime error messages, an accessible API, and, yes, even some language features to mimic dominant paradigms[1] are all ways to do that.

[1] See Brian&#039;s OCaml example above -- I couldn&#039;t remember the for loop syntax when I wrote my comment.</description>
		<content:encoded><![CDATA[<p>@Tracy</p>
<p>In saying we should be sensitive to the limits of gradual adoption, I&#8217;m talking about building hand-holding into language infrastructure based on the assumption that someone knows a mainstream language but is learning yours.  Useful compiler/runtime error messages, an accessible API, and, yes, even some language features to mimic dominant paradigms[1] are all ways to do that.</p>
<p>[1] See Brian&#8217;s OCaml example above &#8212; I couldn&#8217;t remember the for loop syntax when I wrote my comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tracy</title>
		<link>http://enfranchisedmind.com/blog/posts/too-academic-languages/#comment-34449</link>
		<dc:creator>Tracy</dc:creator>
		<pubDate>Mon, 20 Apr 2009 04:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=1079#comment-34449</guid>
		<description>Robert,

I&#039;ve re-read your post a couple times. It&#039;s interesting to hear that Groovy has been more successful than Scala at being adopted, and I hear you to account for the difference by saying that Groovy has facilitated a more gradual adoption route.

Yes, I&#039;m partial to the &quot;Intuitive Means Familiar&quot; idea. It&#039;s not that I think people who fend off so-called &quot;academic&quot; languages are lazy, though. I think each person works from their own cost-benefit analysis, and (like Brian) I think that the estimates of high difficulty tend to be what put people off.

I agree that it would be better if &quot;academic&quot; were not the term used as shorthand. It&#039;s inaccurate and counterproductive.

I also agree that when a language &quot;pushes the envelope&quot; it should not be a surprise when it does not sweep the industry as the new big thing.

What I remain dubious about is the ability to &quot;be sensitive&quot; about the limits to gradual adoption. Are you talking about actual changes to languages, or are you talking about improvements to identifying and communicating ways to help build skill in the (unaltered) languages?</description>
		<content:encoded><![CDATA[<p>Robert,</p>
<p>I&#8217;ve re-read your post a couple times. It&#8217;s interesting to hear that Groovy has been more successful than Scala at being adopted, and I hear you to account for the difference by saying that Groovy has facilitated a more gradual adoption route.</p>
<p>Yes, I&#8217;m partial to the &#8220;Intuitive Means Familiar&#8221; idea. It&#8217;s not that I think people who fend off so-called &#8220;academic&#8221; languages are lazy, though. I think each person works from their own cost-benefit analysis, and (like Brian) I think that the estimates of high difficulty tend to be what put people off.</p>
<p>I agree that it would be better if &#8220;academic&#8221; were not the term used as shorthand. It&#8217;s inaccurate and counterproductive.</p>
<p>I also agree that when a language &#8220;pushes the envelope&#8221; it should not be a surprise when it does not sweep the industry as the new big thing.</p>
<p>What I remain dubious about is the ability to &#8220;be sensitive&#8221; about the limits to gradual adoption. Are you talking about actual changes to languages, or are you talking about improvements to identifying and communicating ways to help build skill in the (unaltered) languages?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
