<?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 on: Lies or Statistics?</title>
	<atom:link href="http://www.javarant.com/2008/01/23/lies-or-statistics/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.javarant.com/2008/01/23/lies-or-statistics/</link>
	<description>Learn the newest innovations in Java and unleash explosive new techniques of the technology age.  JavaRant teaches you how to use the latest strategies with classic principles to help you become an expert in this exciting revolution.  Whether you are new to Java or are a seasoned veteran, you’ll discover new ways to boost your productivity and understanding.  You’ll learn about tools to make you faster, frameworks to aid in applications, servers to make your apps run faster, and much more.  We’re dedicated to teaching you not only the skills but also the mind set necessary to succeed as a Java programmer.  Come join our community that contains thousands of professionals working to keep their edge.</description>
	<pubDate>Sat, 22 Nov 2008 15:00:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Matt</title>
		<link>http://www.javarant.com/2008/01/23/lies-or-statistics/#comment-24</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sat, 23 Feb 2008 16:57:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.javarant.com/2008/01/23/lies-or-statistics/#comment-24</guid>
		<description>It really drives me crazy when I hear people complain about how slow or how fast this language or that language is:  the real cost of the vast majority of computing endeavors is not in cpu cycles but in human resource costs.   Let's say for giggles that Perl runs 10% faster than Java.  I can almost guarantee you that writing, debugging, and maintaining Perl code is a lot more expensive than doing the same in Java.  The labor pool of skilled Java people is also larger than people who are equally good in Lisp.  

And if you are in the situation where you are at 99% cpu utilization and those 3 extra cycles are going to make a real difference, you are running your code on the wrong hardware.  At that point you need to distribute your work across better servers.  It is a simple fact that adding hardware to improve performance is cheaper than rewriting it in another language because Ada or Ruby or Pascal or whatever is too slow.  (And yes, I acknowledge that crappy code will run slow no matter what kind of Cray supercomputer you run it on.)

It's really quite simple:  Language choice should be viewed as an economic decision, not a technical one. When a technical strength or weakness of a language is brought up, the question should be "so what?" --- which is inherently an economic assessment.  Does 5% faster execution translate into noticeably better user satisfaction and retention, or lower costs, or increased sales, or anything else like that?  And does it do so more cost-effectively than the alternatives, when everything else is taken into consideration?</description>
		<content:encoded><![CDATA[<p>It really drives me crazy when I hear people complain about how slow or how fast this language or that language is:  the real cost of the vast majority of computing endeavors is not in cpu cycles but in human resource costs.   Let&#8217;s say for giggles that Perl runs 10% faster than Java.  I can almost guarantee you that writing, debugging, and maintaining Perl code is a lot more expensive than doing the same in Java.  The labor pool of skilled Java people is also larger than people who are equally good in Lisp.  </p>
<p>And if you are in the situation where you are at 99% cpu utilization and those 3 extra cycles are going to make a real difference, you are running your code on the wrong hardware.  At that point you need to distribute your work across better servers.  It is a simple fact that adding hardware to improve performance is cheaper than rewriting it in another language because Ada or Ruby or Pascal or whatever is too slow.  (And yes, I acknowledge that crappy code will run slow no matter what kind of Cray supercomputer you run it on.)</p>
<p>It&#8217;s really quite simple:  Language choice should be viewed as an economic decision, not a technical one. When a technical strength or weakness of a language is brought up, the question should be &#8220;so what?&#8221; &#8212; which is inherently an economic assessment.  Does 5% faster execution translate into noticeably better user satisfaction and retention, or lower costs, or increased sales, or anything else like that?  And does it do so more cost-effectively than the alternatives, when everything else is taken into consideration?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
