<?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: The imminent death of J2ME ?</title>
	<atom:link href="http://www.ovidiuiliescu.com/2009/09/27/the-imminent-death-of-j2me/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ovidiuiliescu.com/2009/09/27/the-imminent-death-of-j2me/</link>
	<description>Quality Software Development Services</description>
	<lastBuildDate>Tue, 15 Feb 2011 00:05:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Dusan</title>
		<link>http://www.ovidiuiliescu.com/2009/09/27/the-imminent-death-of-j2me/comment-page-1/#comment-2084</link>
		<dc:creator>Dusan</dc:creator>
		<pubDate>Tue, 15 Feb 2011 00:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.ovidiuiliescu.com/?p=211#comment-2084</guid>
		<description>&lt;em&gt;My 2 cents, in case anyone is still following this&lt;/em&gt;

“J2ME is slow when compared to the iPhone” - well J2ME runs on a JVM, which at best case is Just in Time compiled. This can&#039;t perform comparably to a natively written app. Naturally the current RIM SDK which is only Java suffers the same fate, but since all apps are written this way users can&#039;t see compare so easily.

“The J2ME API is not nearly as powerful as the iPhone’s” - are you really confident that Java&#039;s new owner (Oracle) is going to keep on updating the platform?

“J2ME suffers badly from device fragmentation issues” - this is actually one I find in J2ME&#039;s favour. Nothing can be more inefficient than rewriting for every platform, which is basically what is required if you go native.


“J2ME applications can’t match the look and feel of the iPhone” - Even if it looked as good, I really doubt you could get the same level of responsiveness. Very difficult to do in any VM environment.

“The iPhone has an ever-growing userbase and will eventually kill J2ME” - although iPhone isn&#039;t competitive at the mid-market, some of the entry level BlackBerries are pretty affordable. Granted, it&#039;s hard to tell whether these will ever be completely dominant in emerging markets. But is that really where the app money is?

“J2ME is not as flexible as the iPhone” - agreed J2ME is the most prevalent mobile API around.

“With so many platforms around, J2ME’s market share is going to dwindle” - I don&#039;t see &quot;smartphone&quot; users accepting J2ME apps anymore.

“Everyone is switching to the iPhone and there won’t be enough developers left to work with J2ME” - of course J2ME has a constant supply of developers from J2SE and J2EE. Java is an easier language than Objective-C. But I would rather code in C than fight on device Java debugging (at least that was my experience with Nokia/Eclipse).

iPhone proved there was a whole economy and ecosystem for app developers (and it proved this in a very short space of time). Has J2ME done the same? What are Oracle&#039;s plans with Java in general?</description>
		<content:encoded><![CDATA[<p><em>My 2 cents, in case anyone is still following this</em></p>
<p>“J2ME is slow when compared to the iPhone” &#8211; well J2ME runs on a JVM, which at best case is Just in Time compiled. This can&#8217;t perform comparably to a natively written app. Naturally the current RIM SDK which is only Java suffers the same fate, but since all apps are written this way users can&#8217;t see compare so easily.</p>
<p>“The J2ME API is not nearly as powerful as the iPhone’s” &#8211; are you really confident that Java&#8217;s new owner (Oracle) is going to keep on updating the platform?</p>
<p>“J2ME suffers badly from device fragmentation issues” &#8211; this is actually one I find in J2ME&#8217;s favour. Nothing can be more inefficient than rewriting for every platform, which is basically what is required if you go native.</p>
<p>“J2ME applications can’t match the look and feel of the iPhone” &#8211; Even if it looked as good, I really doubt you could get the same level of responsiveness. Very difficult to do in any VM environment.</p>
<p>“The iPhone has an ever-growing userbase and will eventually kill J2ME” &#8211; although iPhone isn&#8217;t competitive at the mid-market, some of the entry level BlackBerries are pretty affordable. Granted, it&#8217;s hard to tell whether these will ever be completely dominant in emerging markets. But is that really where the app money is?</p>
<p>“J2ME is not as flexible as the iPhone” &#8211; agreed J2ME is the most prevalent mobile API around.</p>
<p>“With so many platforms around, J2ME’s market share is going to dwindle” &#8211; I don&#8217;t see &#8220;smartphone&#8221; users accepting J2ME apps anymore.</p>
<p>“Everyone is switching to the iPhone and there won’t be enough developers left to work with J2ME” &#8211; of course J2ME has a constant supply of developers from J2SE and J2EE. Java is an easier language than Objective-C. But I would rather code in C than fight on device Java debugging (at least that was my experience with Nokia/Eclipse).</p>
<p>iPhone proved there was a whole economy and ecosystem for app developers (and it proved this in a very short space of time). Has J2ME done the same? What are Oracle&#8217;s plans with Java in general?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mko</title>
		<link>http://www.ovidiuiliescu.com/2009/09/27/the-imminent-death-of-j2me/comment-page-1/#comment-935</link>
		<dc:creator>mko</dc:creator>
		<pubDate>Thu, 30 Sep 2010 15:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.ovidiuiliescu.com/?p=211#comment-935</guid>
		<description>Depends on the intended market.
iPhone is way to expensive on the markets where carriers don&#039;t to contracts. And has way less market share.</description>
		<content:encoded><![CDATA[<p>Depends on the intended market.<br />
iPhone is way to expensive on the markets where carriers don&#8217;t to contracts. And has way less market share.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Livingstone</title>
		<link>http://www.ovidiuiliescu.com/2009/09/27/the-imminent-death-of-j2me/comment-page-1/#comment-487</link>
		<dc:creator>Rich Livingstone</dc:creator>
		<pubDate>Tue, 20 Jul 2010 13:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.ovidiuiliescu.com/?p=211#comment-487</guid>
		<description>I wish that the arguments were technical ones but unfortunately, in the real world, marketing rules and Apple has sold it to the majority of the world, with Android coming up on the outside. I&#039;ve been developing J2ME apps for 5 years but distribution has always been a problem - a problem the iTunes and Android app stores solve. Device fragmentation has always been a huge problem, leading to a tendency for apps not to &quot;just work&quot; - except on iPhones where because control is tight, it does just all work (mostly :-&gt;).

I would bet on Apple at this point to keep and maintain their lead, at least until Google figure out how to prevent fragmentation on the Android platform.</description>
		<content:encoded><![CDATA[<p>I wish that the arguments were technical ones but unfortunately, in the real world, marketing rules and Apple has sold it to the majority of the world, with Android coming up on the outside. I&#8217;ve been developing J2ME apps for 5 years but distribution has always been a problem &#8211; a problem the iTunes and Android app stores solve. Device fragmentation has always been a huge problem, leading to a tendency for apps not to &#8220;just work&#8221; &#8211; except on iPhones where because control is tight, it does just all work (mostly :-&gt;).</p>
<p>I would bet on Apple at this point to keep and maintain their lead, at least until Google figure out how to prevent fragmentation on the Android platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reserver</title>
		<link>http://www.ovidiuiliescu.com/2009/09/27/the-imminent-death-of-j2me/comment-page-1/#comment-409</link>
		<dc:creator>Reserver</dc:creator>
		<pubDate>Thu, 24 Jun 2010 04:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.ovidiuiliescu.com/?p=211#comment-409</guid>
		<description>I totally agree with you, and here is the proof:
http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html 

I think Java and its derivatives are here to stay...particularly now with Oracle at back</description>
		<content:encoded><![CDATA[<p>I totally agree with you, and here is the proof:<br />
<a href="http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html" rel="nofollow">http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html</a> </p>
<p>I think Java and its derivatives are here to stay&#8230;particularly now with Oracle at back</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jj</title>
		<link>http://www.ovidiuiliescu.com/2009/09/27/the-imminent-death-of-j2me/comment-page-1/#comment-403</link>
		<dc:creator>jj</dc:creator>
		<pubDate>Tue, 22 Jun 2010 15:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.ovidiuiliescu.com/?p=211#comment-403</guid>
		<description>For winCE and windows mobile there is phoneME, for Android there is microemulator. Only the iphone doesn&#039;t have a solution for j2me.
For business applications there is no better platform available.</description>
		<content:encoded><![CDATA[<p>For winCE and windows mobile there is phoneME, for Android there is microemulator. Only the iphone doesn&#8217;t have a solution for j2me.<br />
For business applications there is no better platform available.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

