<?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: Is Java &#8220;architecture&#8221; irrelevant?</title>
	<atom:link href="http://www.crazymcphee.net/x/2009/01/30/is-java-architecture-irrelevant/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crazymcphee.net/x/2009/01/30/is-java-architecture-irrelevant/</link>
	<description>programming idiom and methodology</description>
	<lastBuildDate>Tue, 24 Aug 2010 08:56:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: john smith</title>
		<link>http://www.crazymcphee.net/x/2009/01/30/is-java-architecture-irrelevant/comment-page-1/#comment-43</link>
		<dc:creator>john smith</dc:creator>
		<pubDate>Fri, 30 Jan 2009 12:50:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.crazymcphee.net/x/?p=113#comment-43</guid>
		<description>Just because JEE has tons of APIs doesn&#039;t force you to use them all.  We build applications with Tomcat, Struts 1, OJB and Spring and little else.  Our applications can be built fast and work.  We don&#039;t have training issues.  We get the job done.

I agree that if Sun keeps making language changes, it will harm the language.  Young developers feel that if things don&#039;t keep changing, it&#039;s not good.  Experienced developers realize that these changes aren&#039;t necessary and saving a few characters typing in code is so minor in the whole application development process that it&#039;s not worth it.</description>
		<content:encoded><![CDATA[<p>Just because JEE has tons of APIs doesn&#8217;t force you to use them all.  We build applications with Tomcat, Struts 1, OJB and Spring and little else.  Our applications can be built fast and work.  We don&#8217;t have training issues.  We get the job done.</p>
<p>I agree that if Sun keeps making language changes, it will harm the language.  Young developers feel that if things don&#8217;t keep changing, it&#8217;s not good.  Experienced developers realize that these changes aren&#8217;t necessary and saving a few characters typing in code is so minor in the whole application development process that it&#8217;s not worth it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scot Mcphee</title>
		<link>http://www.crazymcphee.net/x/2009/01/30/is-java-architecture-irrelevant/comment-page-1/#comment-42</link>
		<dc:creator>Scot Mcphee</dc:creator>
		<pubDate>Fri, 30 Jan 2009 07:10:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.crazymcphee.net/x/?p=113#comment-42</guid>
		<description>Also the vendors certainly aren&#039;t helping with their super-bloato-products promising all sorts of nirvana if you&#039;ll only swallow their $100,000 graphically-programmed kool-aid.</description>
		<content:encoded><![CDATA[<p>Also the vendors certainly aren&#8217;t helping with their super-bloato-products promising all sorts of nirvana if you&#8217;ll only swallow their $100,000 graphically-programmed kool-aid.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scot Mcphee</title>
		<link>http://www.crazymcphee.net/x/2009/01/30/is-java-architecture-irrelevant/comment-page-1/#comment-41</link>
		<dc:creator>Scot Mcphee</dc:creator>
		<pubDate>Fri, 30 Jan 2009 07:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.crazymcphee.net/x/?p=113#comment-41</guid>
		<description>Simon,

Most certainly the Java EE stack is full of bloat. However I think the number of competing open source solutions to be a blessing, not a curse. I think it&#039;s nearly always possible to find a suitable implementation fairly quickly for any given task, and the choice actually facilitates that.

However I do share the concern that Java EE is becoming too cumbersome and tied up in &#039;standardisation&#039; and it&#039;s not really helping Java in the marketplace.

Additionally I would say that many of the new language features mooted in version 7, combined with the half-baked features from version 5, are also doing real and vital damage to the language. (Annotated, generic-using autoboxed code looks more unreadable by the day). However, that is probably a discussion left for another day.</description>
		<content:encoded><![CDATA[<p>Simon,</p>
<p>Most certainly the Java EE stack is full of bloat. However I think the number of competing open source solutions to be a blessing, not a curse. I think it&#8217;s nearly always possible to find a suitable implementation fairly quickly for any given task, and the choice actually facilitates that.</p>
<p>However I do share the concern that Java EE is becoming too cumbersome and tied up in &#8216;standardisation&#8217; and it&#8217;s not really helping Java in the marketplace.</p>
<p>Additionally I would say that many of the new language features mooted in version 7, combined with the half-baked features from version 5, are also doing real and vital damage to the language. (Annotated, generic-using autoboxed code looks more unreadable by the day). However, that is probably a discussion left for another day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Mittag</title>
		<link>http://www.crazymcphee.net/x/2009/01/30/is-java-architecture-irrelevant/comment-page-1/#comment-40</link>
		<dc:creator>Simon Mittag</dc:creator>
		<pubDate>Fri, 30 Jan 2009 06:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.crazymcphee.net/x/?p=113#comment-40</guid>
		<description>Hi Scott,

I take your point about architecture not necessarily being framework choice. As I&#039;ve already posted, I think being less prescriptive is actually doing more for you.

What I meant by irrelevant Java architecture in the title is the internal state of the whole Java EE stack, both JSR and Open Source, i.e. how many MVC frameworks and XML standards does the world need?

In a simpler environment, the developer would be free from such choice, which in most cases should be a good thing actually.

I guess the main part I am a bit hung up with is that with problems come solutions, come generalization and standards to make things easier (or OSS alternatives). However all that happens is that these standards are being added to a huge existing pile. Nobody ever takes anything out (difficult with OSS), so while we attempt to make things easier we actually make them more difficult to understand and they begin to disagree with each other.

This may be just the natural effects of aging though? I&#039;m not sure.

Cheers,

Simon</description>
		<content:encoded><![CDATA[<p>Hi Scott,</p>
<p>I take your point about architecture not necessarily being framework choice. As I&#8217;ve already posted, I think being less prescriptive is actually doing more for you.</p>
<p>What I meant by irrelevant Java architecture in the title is the internal state of the whole Java EE stack, both JSR and Open Source, i.e. how many MVC frameworks and XML standards does the world need?</p>
<p>In a simpler environment, the developer would be free from such choice, which in most cases should be a good thing actually.</p>
<p>I guess the main part I am a bit hung up with is that with problems come solutions, come generalization and standards to make things easier (or OSS alternatives). However all that happens is that these standards are being added to a huge existing pile. Nobody ever takes anything out (difficult with OSS), so while we attempt to make things easier we actually make them more difficult to understand and they begin to disagree with each other.</p>
<p>This may be just the natural effects of aging though? I&#8217;m not sure.</p>
<p>Cheers,</p>
<p>Simon</p>
]]></content:encoded>
	</item>
</channel>
</rss>
