<?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: Bay Area Mobility Forum</title>
	<atom:link href="http://billday.com/2004/08/08/bay-area-mobility-forum/feed/" rel="self" type="application/rss+xml" />
	<link>http://billday.com/2004/08/08/bay-area-mobility-forum/</link>
	<description>Thoughts on software development and mobility</description>
	<pubDate>Tue, 06 Jan 2009 13:14:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BillDay.com &#187; BAMF &#8220;J2ME at Five&#8221; slides</title>
		<link>http://billday.com/2004/08/08/bay-area-mobility-forum/comment-page-1/#comment-2657</link>
		<dc:creator>BillDay.com &#187; BAMF &#8220;J2ME at Five&#8221; slides</dc:creator>
		<pubDate>Fri, 21 Oct 2005 16:48:06 +0000</pubDate>
		<guid isPermaLink="false">/?p=164#comment-2657</guid>
		<description>[...] I&#8217;ve posted slides for my Bay Area Mobility Forum presentation &#8220;J2ME at Five: Where We&#8217;ve Been, and Where We&#8217;ll Be at Ten&#8221; . Click here to access the slides. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve posted slides for my Bay Area Mobility Forum presentation &#8220;J2ME at Five: Where We&#8217;ve Been, and Where We&#8217;ll Be at Ten&#8221; . Click here to access the slides. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Day</title>
		<link>http://billday.com/2004/08/08/bay-area-mobility-forum/comment-page-1/#comment-216</link>
		<dc:creator>Bill Day</dc:creator>
		<pubDate>Mon, 23 Aug 2004 16:27:21 +0000</pubDate>
		<guid isPermaLink="false">/?p=164#comment-216</guid>
		<description>I appreciate your comments but must respectfully disagree on a number of your points.  Or at the least, qualify some of them.

While I agree that Microsoft sometimes does a better job of publicizing and "talking up" what they do have, that doesn't mean that other options don't exist, it simply means we (in this case the Java Community in general and Nokia and me specifically) have even more evangelism work to do.

In fact, Nokia has a large and growing catalog of J2ME applications (the usual suspects such as games but also personal productivity, business and enterprise, vertical industry, and other applications).  See &lt;a href="http://billday.com/2004/07/11"&gt;my earlier post on my Nokia 7610&lt;/a&gt; for a link to a small sample of some of the latest in the Forum Nokia application catalog.

There is always more to do, though, and I agree that we need to do it aggressively, and now.  I would appreciate any specific suggestions or requests you have as I work to do my part for Nokia and the J2ME development community at large.</description>
		<content:encoded><![CDATA[<p>I appreciate your comments but must respectfully disagree on a number of your points.  Or at the least, qualify some of them.</p>
<p>While I agree that Microsoft sometimes does a better job of publicizing and &#8220;talking up&#8221; what they do have, that doesn&#8217;t mean that other options don&#8217;t exist, it simply means we (in this case the Java Community in general and Nokia and me specifically) have even more evangelism work to do.</p>
<p>In fact, Nokia has a large and growing catalog of J2ME applications (the usual suspects such as games but also personal productivity, business and enterprise, vertical industry, and other applications).  See <a href="http://billday.com/2004/07/11">my earlier post on my Nokia 7610</a> for a link to a small sample of some of the latest in the Forum Nokia application catalog.</p>
<p>There is always more to do, though, and I agree that we need to do it aggressively, and now.  I would appreciate any specific suggestions or requests you have as I work to do my part for Nokia and the J2ME development community at large.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Shelton</title>
		<link>http://billday.com/2004/08/08/bay-area-mobility-forum/comment-page-1/#comment-214</link>
		<dc:creator>Ted Shelton</dc:creator>
		<pubDate>Sat, 21 Aug 2004 13:58:27 +0000</pubDate>
		<guid isPermaLink="false">/?p=164#comment-214</guid>
		<description>Sorry I missed your presentation for BAMF -- Your view on J2ME is interesting from a handset perspective but is missing a developer perspective.  How many developers are really out there in the world writing J2ME apps?  NOT Java apps -- there is a big difference between a J2EE developer and a J2ME developer... and where is the development community?  Components?  Publications?  This is where J2ME is failing.  Compare to the community developing around Microsoft's PocketPC and Phone Edition communities -- a tradition much more familiar with client side application development.  A miniscule number of devices compared to J2ME -- and yet an order of magnitude more applications...  Handset manufacturers will have to correct this development community deficiency or they will lose to Microsoft in the long run.</description>
		<content:encoded><![CDATA[<p>Sorry I missed your presentation for BAMF &#8212; Your view on J2ME is interesting from a handset perspective but is missing a developer perspective.  How many developers are really out there in the world writing J2ME apps?  NOT Java apps &#8212; there is a big difference between a J2EE developer and a J2ME developer&#8230; and where is the development community?  Components?  Publications?  This is where J2ME is failing.  Compare to the community developing around Microsoft&#8217;s PocketPC and Phone Edition communities &#8212; a tradition much more familiar with client side application development.  A miniscule number of devices compared to J2ME &#8212; and yet an order of magnitude more applications&#8230;  Handset manufacturers will have to correct this development community deficiency or they will lose to Microsoft in the long run.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
