<?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: Continous Tax?</title>
	<atom:link href="http://almaer.com/blog/continous-tax/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/continous-tax</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Carl Gundel</title>
		<link>http://almaer.com/blog/continous-tax/comment-page-1#comment-37540</link>
		<dc:creator>Carl Gundel</dc:creator>
		<pubDate>Wed, 10 Oct 2007 21:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/continous-tax#comment-37540</guid>
		<description>I have spent many thousands of hours coding in Smalltalk and Java.  Both have their strengths and weaknesses.

Java&#039;s static typing system is only a strength in that it makes it easy to write certain kinds of tools.  These tools only partially make up for the very type system they are enabled by.  Type declarations make up for a lot of noise in Java code, and Java&#039;s broken polymorphism is remedied by interfaces (which perhaps would be a nice language feature in better circumstances) which proliferate and cause cognitive overload because there are after a time too many pieces in the code to keep juggling in your mind.

Smalltalk&#039;s dynamic typing makes writing clear and expressive code a simple matter.  The importance of this cannot be overestimated.  While there are a few refactorings that cannot be done in a dynamic language, there are refactoring tools for Smalltalk (and Groovy too I gather) and have been long before Java had them.  Smalltalk cooperates so well with the mental processes of object oriented development that static type declarations only get in the your way.

My 20 cents</description>
		<content:encoded><![CDATA[<p>I have spent many thousands of hours coding in Smalltalk and Java.  Both have their strengths and weaknesses.</p>
<p>Java&#8217;s static typing system is only a strength in that it makes it easy to write certain kinds of tools.  These tools only partially make up for the very type system they are enabled by.  Type declarations make up for a lot of noise in Java code, and Java&#8217;s broken polymorphism is remedied by interfaces (which perhaps would be a nice language feature in better circumstances) which proliferate and cause cognitive overload because there are after a time too many pieces in the code to keep juggling in your mind.</p>
<p>Smalltalk&#8217;s dynamic typing makes writing clear and expressive code a simple matter.  The importance of this cannot be overestimated.  While there are a few refactorings that cannot be done in a dynamic language, there are refactoring tools for Smalltalk (and Groovy too I gather) and have been long before Java had them.  Smalltalk cooperates so well with the mental processes of object oriented development that static type declarations only get in the your way.</p>
<p>My 20 cents</p>
]]></content:encoded>
	</item>
</channel>
</rss>
