<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Rocky is right; software is too hard</title>
	<atom:link href="http://craigrandall.net/archives/2006/05/software-is-too-hard/feed/" rel="self" type="application/rss+xml" />
	<link>http://craigrandall.net/archives/2006/05/software-is-too-hard/</link>
	<description>Thoughts about software architecture, books and life</description>
	<lastBuildDate>Wed, 04 Jan 2012 18:00:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Craig&#8217;s Musings &#187; Blog Archive &#187; I&#8217;m starting to see red</title>
		<link>http://craigrandall.net/archives/2006/05/software-is-too-hard/comment-page-1/#comment-1239</link>
		<dc:creator>Craig&#8217;s Musings &#187; Blog Archive &#187; I&#8217;m starting to see red</dc:creator>
		<pubDate>Sun, 03 Sep 2006 21:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://craigrandall.net/archives/2006/05/software-is-too-hard/#comment-1239</guid>
		<description>[...] While I may cumulatively spend a majority time and passion developing on Windows in .NET et al during my career, I also work with a significant Java code base at work. IMHO, both of these platforms overshoot the needs of classes of solutions with burdensome (not pervasive)&#160;runtimes, prolific APIs, and layer upon layer of functionality with sometimes questionable value (e.g. does this layer justify another part of the underlying platform, framework or toolset, or does this layer yield clear business value?). For example, my previous post about WS-* pain relief is as much about Java&#8217;s WS-* implementation as WS-* itself. (FWIW, I prefer Microsoft&#8217;s approach in Windows Communication Foundation, which just went Release Candidate, by the way.) [...]</description>
		<content:encoded><![CDATA[<p>[...] While I may cumulatively spend a majority time and passion developing on Windows in .NET et al during my career, I also work with a significant Java code base at work. IMHO, both of these platforms overshoot the needs of classes of solutions with burdensome (not pervasive)&nbsp;runtimes, prolific APIs, and layer upon layer of functionality with sometimes questionable value (e.g. does this layer justify another part of the underlying platform, framework or toolset, or does this layer yield clear business value?). For example, my previous post about WS-* pain relief is as much about Java&#8217;s WS-* implementation as WS-* itself. (FWIW, I prefer Microsoft&#8217;s approach in Windows Communication Foundation, which just went Release Candidate, by the way.) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

