<?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: Top 5 Reasons Why Java Applets Failed</title>
	<atom:link href="http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/</link>
	<description>Simon Brocklehurst's Technology Blog</description>
	<pubDate>Sun, 23 Nov 2008 10:22:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Bilica Ionut</title>
		<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-486040</link>
		<dc:creator>Bilica Ionut</dc:creator>
		<pubDate>Wed, 23 Jul 2008 06:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-486040</guid>
		<description>I agree with no. 4 only. Seems to me that java it's too serious for web developers. Anyway, I've really worked a lot with applets and you could look at my masterpiece: http://www.craiovamap.ro/harta-craiovei
It's an interactive map for my town, hope you like it.</description>
		<content:encoded><![CDATA[<p>I agree with no. 4 only. Seems to me that java it&#8217;s too serious for web developers. Anyway, I&#8217;ve really worked a lot with applets and you could look at my masterpiece: <a href="http://www.craiovamap.ro/harta-craiovei" rel="nofollow">http://www.craiovamap.ro/harta-craiovei</a><br />
It&#8217;s an interactive map for my town, hope you like it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon</title>
		<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-217442</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Wed, 16 Jan 2008 09:05:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-217442</guid>
		<description>Dominic,

Clearly, versioning is very important, and it's good that Sun seems to be addressing this.  We might have to agree to disagree that it's the No. 1 reason why applets failed though....

By the way, I'm seeing increasing numbers of problems with Flash e.g. causing browser crashes in particular browsers; the Flash software simply not running in the browser or locking up etc.</description>
		<content:encoded><![CDATA[<p>Dominic,</p>
<p>Clearly, versioning is very important, and it&#8217;s good that Sun seems to be addressing this.  We might have to agree to disagree that it&#8217;s the No. 1 reason why applets failed though&#8230;.</p>
<p>By the way, I&#8217;m seeing increasing numbers of problems with Flash e.g. causing browser crashes in particular browsers; the Flash software simply not running in the browser or locking up etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dominic Cioccarelli</title>
		<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-217019</link>
		<dc:creator>Dominic Cioccarelli</dc:creator>
		<pubDate>Wed, 16 Jan 2008 01:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-217019</guid>
		<description>Hi Simon,

much as I like applets I think that you missed the major reason why the failed: version incompatibility. As soon as Java 1.1 came out we started to see the issues. Microsoft didn't make it any easier with thir JVM, but Sun nver fully addressed the issue.

The latest Java plug in is much better and WebStart isn't too bad but Sun have always fallen short in addressing that final 20 percent of how their technology performs in the real world. Macromedia on the other hand have got it right. How many times do you come across Flash incompatibility issues?

I've seen so many instances of applets configured to use a specific JVM version even though it may work on another version. Developers should (but don't) compile their code for the earliest version of the JVM possible (see the "-target" flag!). Often Java is packaged with commercial Java applications just to ensure that the correct version is used.

Worse still, when the Java decides that an update is required / available (even for a point release) it installs a completely new Java environment (so you end up with jre_1_5_0, jre_1_5_1, jre_1_5_2, jre_1_5_3, etc. which are all 100Mb in side, just to cater for apps which might have a dependency on a specific bug in a specific point release).

For me, version is what lets Java down in terms of running applets. For server side apps this is a non issue which is why Java has prospered there.

Dominic Cioccarelli.</description>
		<content:encoded><![CDATA[<p>Hi Simon,</p>
<p>much as I like applets I think that you missed the major reason why the failed: version incompatibility. As soon as Java 1.1 came out we started to see the issues. Microsoft didn&#8217;t make it any easier with thir JVM, but Sun nver fully addressed the issue.</p>
<p>The latest Java plug in is much better and WebStart isn&#8217;t too bad but Sun have always fallen short in addressing that final 20 percent of how their technology performs in the real world. Macromedia on the other hand have got it right. How many times do you come across Flash incompatibility issues?</p>
<p>I&#8217;ve seen so many instances of applets configured to use a specific JVM version even though it may work on another version. Developers should (but don&#8217;t) compile their code for the earliest version of the JVM possible (see the &#8220;-target&#8221; flag!). Often Java is packaged with commercial Java applications just to ensure that the correct version is used.</p>
<p>Worse still, when the Java decides that an update is required / available (even for a point release) it installs a completely new Java environment (so you end up with jre_1_5_0, jre_1_5_1, jre_1_5_2, jre_1_5_3, etc. which are all 100Mb in side, just to cater for apps which might have a dependency on a specific bug in a specific point release).</p>
<p>For me, version is what lets Java down in terms of running applets. For server side apps this is a non issue which is why Java has prospered there.</p>
<p>Dominic Cioccarelli.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon</title>
		<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-185870</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Fri, 21 Dec 2007 12:55:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-185870</guid>
		<description>Yes... although solutions to these problems with Java are now being actively addressed.  In 2008, people should expect Java to behave much better in the browser...

See:

http://www.psynixis.com/blog/2007/12/12/some-new-consumer-java-technologies-to-watch/</description>
		<content:encoded><![CDATA[<p>Yes&#8230; although solutions to these problems with Java are now being actively addressed.  In 2008, people should expect Java to behave much better in the browser&#8230;</p>
<p>See:</p>
<p><a href="http://www.psynixis.com/blog/2007/12/12/some-new-consumer-java-technologies-to-watch/" rel="nofollow">http://www.psynixis.com/blog/2007/12/12/some-new-consumer-java-technologies-to-watch/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Vaughan</title>
		<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-185121</link>
		<dc:creator>Daniel Vaughan</dc:creator>
		<pubDate>Fri, 21 Dec 2007 00:53:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-185121</guid>
		<description>Hi Simon, 

Interesting and timely post. You're spot on with your points. The main difference I see with Silverlight, Flash, and Java, is that the first two are much 'lighter' compared to Java in the browser.
On Windows, when I reach a page with an applet, my hard drive starts whirring, the system becomes less responsive, and I see the JVM icon appear in the tray. I usually think to myself "oh no, this will take a while."

Daniel</description>
		<content:encoded><![CDATA[<p>Hi Simon, </p>
<p>Interesting and timely post. You&#8217;re spot on with your points. The main difference I see with Silverlight, Flash, and Java, is that the first two are much &#8216;lighter&#8217; compared to Java in the browser.<br />
On Windows, when I reach a page with an applet, my hard drive starts whirring, the system becomes less responsive, and I see the JVM icon appear in the tray. I usually think to myself &#8220;oh no, this will take a while.&#8221;</p>
<p>Daniel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S&#233;bastien Let&#233;li&#233; and Cyril Balit weblog - Java, Javascript, Eclipse, RCP, RIA, SOA, AJAX, WPF, Swing, SWT, JFace, Web Services, REST</title>
		<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-52655</link>
		<dc:creator>S&#233;bastien Let&#233;li&#233; and Cyril Balit weblog - Java, Javascript, Eclipse, RCP, RIA, SOA, AJAX, WPF, Swing, SWT, JFace, Web Services, REST</dc:creator>
		<pubDate>Fri, 18 May 2007 13:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-52655</guid>
		<description>[...] desktop (RDA). Sun a donc Ã©tÃ© prÃ©curseur dans ce domaine mais l&#8217;Applet n&#8217;a pas sÃ©duit et c&#8217;est la que Silverlight et Flex marquent un point car ils disposent d&#8217;outils de [...]</description>
		<content:encoded><![CDATA[<p>[...] desktop (RDA). Sun a donc Ã©tÃ© prÃ©curseur dans ce domaine mais l&#8217;Applet n&#8217;a pas sÃ©duit et c&#8217;est la que Silverlight et Flex marquent un point car ils disposent d&#8217;outils de [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S&#233;bastien Let&#233;li&#233; and Cyril Balit weblog - Java, Javascript, Eclipse, RCP, RIA, SOA, AJAX, WPF, Swing, SWT, JFace, Web Services, REST</title>
		<link>http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-52654</link>
		<dc:creator>S&#233;bastien Let&#233;li&#233; and Cyril Balit weblog - Java, Javascript, Eclipse, RCP, RIA, SOA, AJAX, WPF, Swing, SWT, JFace, Web Services, REST</dc:creator>
		<pubDate>Fri, 18 May 2007 13:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/05/03/top-5-reasons-why-java-applets-failed/#comment-52654</guid>
		<description>[...] the deployment of RDA applications. Sun was in advance in this domain but Applet don&#8217;t find success and it&#8217;s the asset of Silverlight and Flex because they have GUI design tool (Expression Web, [...]</description>
		<content:encoded><![CDATA[<p>[...] the deployment of RDA applications. Sun was in advance in this domain but Applet don&#8217;t find success and it&#8217;s the asset of Silverlight and Flex because they have GUI design tool (Expression Web, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
