<?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"
	>
<channel>
	<title>Comments for Ola Bini: Programming Language Synchronicity</title>
	<atom:link href="http://olabini.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://olabini.com/blog</link>
	<description>Ruby, Java, Lisp, Io, JRuby. Programming language archeology, creation and discovery.</description>
	<pubDate>Wed, 16 May 2012 22:48:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>Comment on Announcing JesCov - JavaScript code coverage by JavaScript &#124; Pearltrees</title>
		<link>http://olabini.com/blog/2011/11/announcing-jescov-javascript-code-coverage/#comment-102228</link>
		<dc:creator>JavaScript &#124; Pearltrees</dc:creator>
		<pubDate>Mon, 19 Mar 2012 17:28:48 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=774#comment-102228</guid>
		<description>[...] It seems the JavaScript tool space is not completely saturated yet. As I mentioned in my previous post I’ve had particular trouble finding a good solution to code coverage. So I decided to build my own version of it. The specific feature to notice is transparent translation of source code and support for branch coverage. It also has some limitations at the moment, of course. This is release 0.0.1 and as such is definitely a first release. Announcing JesCov - JavaScript code coverage &#124; Ola Bini: Programming Language Synchronicity [...]</description>
		<content:encoded><![CDATA[<p>[...] It seems the JavaScript tool space is not completely saturated yet. As I mentioned in my previous post I’ve had particular trouble finding a good solution to code coverage. So I decided to build my own version of it. The specific feature to notice is transparent translation of source code and support for branch coverage. It also has some limitations at the moment, of course. This is release 0.0.1 and as such is definitely a first release. Announcing JesCov - JavaScript code coverage | Ola Bini: Programming Language Synchronicity [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Destructuring extravaganza by Idran</title>
		<link>http://olabini.com/blog/2010/03/destructuring-extravaganza/#comment-97466</link>
		<dc:creator>Idran</dc:creator>
		<pubDate>Fri, 02 Mar 2012 08:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=697#comment-97466</guid>
		<description>As far as I could tell there's not support for "variadic destructing" or what you'd might call it. I'm thinking along the lines of e.g. Perl's wantarray (only useful for single vs many) or Perl's Want modules that can tell you the number of wanted return values. Matlab makes heavy use of variables number of return values, and Perl's wantarray can be pretty useful at times. I'm thinking maybe it can be useful in a more general case applying to any destructable data structure. Are there any plans/ideas for this in Ioke/Seph?</description>
		<content:encoded><![CDATA[<p>As far as I could tell there&#8217;s not support for &#8220;variadic destructing&#8221; or what you&#8217;d might call it. I&#8217;m thinking along the lines of e.g. Perl&#8217;s wantarray (only useful for single vs many) or Perl&#8217;s Want modules that can tell you the number of wanted return values. Matlab makes heavy use of variables number of return values, and Perl&#8217;s wantarray can be pretty useful at times. I&#8217;m thinking maybe it can be useful in a more general case applying to any destructable data structure. Are there any plans/ideas for this in Ioke/Seph?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by Learning new languages and their expressiveness &#171; Open sauce code</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-96786</link>
		<dc:creator>Learning new languages and their expressiveness &#171; Open sauce code</dc:creator>
		<pubDate>Tue, 28 Feb 2012 11:09:46 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-96786</guid>
		<description>[...] for us to write code. By easier I don&#8217;t mean we are writing simpler code. As Ola Bini points out in his blog programmers are wanting a higher level of expressiveness. To do this, we have to make some [...]</description>
		<content:encoded><![CDATA[<p>[...] for us to write code. By easier I don&#8217;t mean we are writing simpler code. As Ola Bini points out in his blog programmers are wanting a higher level of expressiveness. To do this, we have to make some [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by It&#8217;s the familiarity model! &#171; Affiliates-test.BlogNotions - Thoughts from Industry Experts</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-95896</link>
		<dc:creator>It&#8217;s the familiarity model! &#171; Affiliates-test.BlogNotions - Thoughts from Industry Experts</dc:creator>
		<pubDate>Thu, 23 Feb 2012 21:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-95896</guid>
		<description>[...] during the same time Ola Bini blogged about expressiveness in programming language syntax. He mentions that a well designed syntax should [...]</description>
		<content:encoded><![CDATA[<p>[...] during the same time Ola Bini blogged about expressiveness in programming language syntax. He mentions that a well designed syntax should [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by Tom Novelli</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-95884</link>
		<dc:creator>Tom Novelli</dc:creator>
		<pubDate>Thu, 23 Feb 2012 18:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-95884</guid>
		<description>I don't know if APL has much of a chance. Popular C-family languages (Javascript, Python, Ruby, etc) also have concise visual symbols. I guess the APL family's advantage is having symbols for functional operations.

Classic APL lacks modern control structuers and isn't suitable for things like imperative loops. I had an idea to embed APL expressions in Lisp to provide control structures... actually started a little prototype implementation; should put it on Github...</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if APL has much of a chance. Popular C-family languages (Javascript, Python, Ruby, etc) also have concise visual symbols. I guess the APL family&#8217;s advantage is having symbols for functional operations.</p>
<p>Classic APL lacks modern control structuers and isn&#8217;t suitable for things like imperative loops. I had an idea to embed APL expressions in Lisp to provide control structures&#8230; actually started a little prototype implementation; should put it on Github&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by Optimising for typing at Mark Needham</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-95571</link>
		<dc:creator>Optimising for typing at Mark Needham</dc:creator>
		<pubDate>Tue, 21 Feb 2012 22:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-95571</guid>
		<description>[...] colleague Ola Bini recently wrote a post describing his thoughts on the syntax of programming languages and while the post in general is interesting the bit that most resonates with me at the moment is [...]</description>
		<content:encoded><![CDATA[<p>[...] colleague Ola Bini recently wrote a post describing his thoughts on the syntax of programming languages and while the post in general is interesting the bit that most resonates with me at the moment is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by Syntax Matters in Slang &#171; Villane</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-94867</link>
		<dc:creator>Syntax Matters in Slang &#171; Villane</dc:creator>
		<pubDate>Thu, 16 Feb 2012 20:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-94867</guid>
		<description>[...] post was inspired by Ola Bini&#8217;s notes on syntax. I agree with most of Ola&#8217;s thoughts. I&#8217;m not convinced that repetition aids reading or [...]</description>
		<content:encoded><![CDATA[<p>[...] post was inspired by Ola Bini&#8217;s notes on syntax. I agree with most of Ola&#8217;s thoughts. I&#8217;m not convinced that repetition aids reading or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by Michael Feathers</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-94843</link>
		<dc:creator>Michael Feathers</dc:creator>
		<pubDate>Thu, 16 Feb 2012 15:25:37 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-94843</guid>
		<description>I generally agree with your blog, but thing that I'm not sure about is whether languages should be optimized for readability over writability.  I think that when things are going well in a language, it's a false dichotomy.

There's research out there that indicates that "conciseness is better" when it comes to syntactic elements: http://www.scala-lang.org/node/3069

It seems to me that if we believe that concise is better, ease in reading and writing and aren't at odds except in the case where very concise constructs can be mistaken for each other.  I don't know enough J or K to know if experienced readers have that problem with them, but it does to me that if that problem is tractable, we're headed toward the APL-ish, J-ish, K-ish languages.</description>
		<content:encoded><![CDATA[<p>I generally agree with your blog, but thing that I&#8217;m not sure about is whether languages should be optimized for readability over writability.  I think that when things are going well in a language, it&#8217;s a false dichotomy.</p>
<p>There&#8217;s research out there that indicates that &#8220;conciseness is better&#8221; when it comes to syntactic elements: <a href="http://www.scala-lang.org/node/3069" rel="nofollow">http://www.scala-lang.org/node/3069</a></p>
<p>It seems to me that if we believe that concise is better, ease in reading and writing and aren&#8217;t at odds except in the case where very concise constructs can be mistaken for each other.  I don&#8217;t know enough J or K to know if experienced readers have that problem with them, but it does to me that if that problem is tractable, we&#8217;re headed toward the APL-ish, J-ish, K-ish languages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by The old problem &#171; Polyglot Posturings</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-94521</link>
		<dc:creator>The old problem &#171; Polyglot Posturings</dc:creator>
		<pubDate>Tue, 14 Feb 2012 12:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-94521</guid>
		<description>[...] Notes on syntax (olabini.com) [...]</description>
		<content:encoded><![CDATA[<p>[...] Notes on syntax (olabini.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Notes on syntax by J. B. Rainsberger</title>
		<link>http://olabini.com/blog/2012/02/notes-on-syntax/#comment-94424</link>
		<dc:creator>J. B. Rainsberger</dc:creator>
		<pubDate>Mon, 13 Feb 2012 21:55:23 +0000</pubDate>
		<guid isPermaLink="false">http://olabini.com/blog/?p=776#comment-94424</guid>
		<description>All notation comes from removing duplication: I write something often, so I want a shorthand for it.</description>
		<content:encoded><![CDATA[<p>All notation comes from removing duplication: I write something often, so I want a shorthand for it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

