<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_03_04_2039212</id>
	<title>Where Android Beats the iPhone</title>
	<author>timothy</author>
	<datestamp>1267698120000</datestamp>
	<htmltext><a href="http://www.infoworld.com/" rel="nofollow">snydeq</a> writes <i>"Peter Wayner provides a <a href="http://www.infoworld.com/d/developer-world/where-android-beats-iphone-397">developer's comparison of Android and the iPhone</a> and finds Android not only competitive but in fact a better choice than the iPhone for many developers, largely due to its Java foundation. 'While iPhone developers have found that one path to success is <a href="http://radar.oreilly.com/2010/01/iphoning-his-way-to-retirement.html">playing to our baser instincts</a> (until <a href="http://techcrunch.com/2010/02/20/app-store-rules-sexy/">Apple shuts them down</a>), a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket,' Wayner writes, pointing out GScript and Remote DB as two powerful tools for developers to make rough but workable custom tools for Android. But the real gem is Java: 'The pure Java foundation of Android will be one of the biggest attractions for many businesses with Java programmers on the staff. Any Java developer familiar with Eclipse should be able to use Google's Android documentation to turn out a very basic application in just a few hours. Not only that, but all of the code from other Java programs will run on your Android phone &mdash; although it won't look pretty or run as fast as it does on multicore servers.'"</i></htmltext>
<tokenext>snydeq writes " Peter Wayner provides a developer 's comparison of Android and the iPhone and finds Android not only competitive but in fact a better choice than the iPhone for many developers , largely due to its Java foundation .
'While iPhone developers have found that one path to success is playing to our baser instincts ( until Apple shuts them down ) , a number of Android applications are offering practical solutions that unlock the power of a phone that 's really a Unix machine you can slip into your pocket, ' Wayner writes , pointing out GScript and Remote DB as two powerful tools for developers to make rough but workable custom tools for Android .
But the real gem is Java : 'The pure Java foundation of Android will be one of the biggest attractions for many businesses with Java programmers on the staff .
Any Java developer familiar with Eclipse should be able to use Google 's Android documentation to turn out a very basic application in just a few hours .
Not only that , but all of the code from other Java programs will run on your Android phone    although it wo n't look pretty or run as fast as it does on multicore servers .
' "</tokentext>
<sentencetext>snydeq writes "Peter Wayner provides a developer's comparison of Android and the iPhone and finds Android not only competitive but in fact a better choice than the iPhone for many developers, largely due to its Java foundation.
'While iPhone developers have found that one path to success is playing to our baser instincts (until Apple shuts them down), a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket,' Wayner writes, pointing out GScript and Remote DB as two powerful tools for developers to make rough but workable custom tools for Android.
But the real gem is Java: 'The pure Java foundation of Android will be one of the biggest attractions for many businesses with Java programmers on the staff.
Any Java developer familiar with Eclipse should be able to use Google's Android documentation to turn out a very basic application in just a few hours.
Not only that, but all of the code from other Java programs will run on your Android phone — although it won't look pretty or run as fast as it does on multicore servers.
'"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365204</id>
	<title>Re:wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267708680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I don't buy apple products because I don't want to support closed system businesses.</p><p>When you support closed system you vote with your dollars to promote that kind of system in your future.</p><p>Fuck that and fuck the future wherein we all have thin clients and 'the cloud' does all our storing and processing.  A poem I write about my wife has no business in a fucking cloud and its inherent security issues; nor does the display and editing of it necessitate monthly subscriptions for access.</p><p>Don't be one of the wide group of idiots that will fund and determine the closed outcome of computing.  Don't support bullshit tech like the ipod/ipad/iphone.</p><p>Support freedom.  Chances are people won't realize that computer freedom mattered until there aren't any choices left to make.</p></htmltext>
<tokenext>I do n't buy apple products because I do n't want to support closed system businesses.When you support closed system you vote with your dollars to promote that kind of system in your future.Fuck that and fuck the future wherein we all have thin clients and 'the cloud ' does all our storing and processing .
A poem I write about my wife has no business in a fucking cloud and its inherent security issues ; nor does the display and editing of it necessitate monthly subscriptions for access.Do n't be one of the wide group of idiots that will fund and determine the closed outcome of computing .
Do n't support bullshit tech like the ipod/ipad/iphone.Support freedom .
Chances are people wo n't realize that computer freedom mattered until there are n't any choices left to make .</tokentext>
<sentencetext>I don't buy apple products because I don't want to support closed system businesses.When you support closed system you vote with your dollars to promote that kind of system in your future.Fuck that and fuck the future wherein we all have thin clients and 'the cloud' does all our storing and processing.
A poem I write about my wife has no business in a fucking cloud and its inherent security issues; nor does the display and editing of it necessitate monthly subscriptions for access.Don't be one of the wide group of idiots that will fund and determine the closed outcome of computing.
Don't support bullshit tech like the ipod/ipad/iphone.Support freedom.
Chances are people won't realize that computer freedom mattered until there aren't any choices left to make.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948</id>
	<title>wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267702860000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>You can buy and play FIFA10 or even Grand Theft Auto on the iPhone. The games are a pretty good indicator IMHO. When complex and expensive productions from big studios start coming out for a platform, you know that the platform is popular.</p><p>And if you think Java makes any kind of difference, think again. The guys that are developing these applications do not seem to care. It's not about happy programmers, it's about happy users. And right now the iPhone still has the edge.</p></htmltext>
<tokenext>You can buy and play FIFA10 or even Grand Theft Auto on the iPhone .
The games are a pretty good indicator IMHO .
When complex and expensive productions from big studios start coming out for a platform , you know that the platform is popular.And if you think Java makes any kind of difference , think again .
The guys that are developing these applications do not seem to care .
It 's not about happy programmers , it 's about happy users .
And right now the iPhone still has the edge .</tokentext>
<sentencetext>You can buy and play FIFA10 or even Grand Theft Auto on the iPhone.
The games are a pretty good indicator IMHO.
When complex and expensive productions from big studios start coming out for a platform, you know that the platform is popular.And if you think Java makes any kind of difference, think again.
The guys that are developing these applications do not seem to care.
It's not about happy programmers, it's about happy users.
And right now the iPhone still has the edge.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364402</id>
	<title>The only thing that counts.</title>
	<author>codepunk</author>
	<datestamp>1267704720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Having built some rather processor heavy apps for the iphone the only thing that counts to me is to be able to utilize every single cpu cycle. Writing apps for these devices is easy, writing apps that can perform is another matter entirely.</p></htmltext>
<tokenext>Having built some rather processor heavy apps for the iphone the only thing that counts to me is to be able to utilize every single cpu cycle .
Writing apps for these devices is easy , writing apps that can perform is another matter entirely .</tokentext>
<sentencetext>Having built some rather processor heavy apps for the iphone the only thing that counts to me is to be able to utilize every single cpu cycle.
Writing apps for these devices is easy, writing apps that can perform is another matter entirely.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364728</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>MrCrassic</author>
	<datestamp>1267706040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Mod parent up. This is not troll material; in fact, it has a really good point.</p></htmltext>
<tokenext>Mod parent up .
This is not troll material ; in fact , it has a really good point .</tokentext>
<sentencetext>Mod parent up.
This is not troll material; in fact, it has a really good point.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368154</id>
	<title>Re:Developers Developers Developers</title>
	<author>rdnetto</author>
	<datestamp>1267819560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It matters when you're both. That said, I avoided Android cause of its Java foundation and got a N900. haven't regretted it for a second<nobr> <wbr></nobr>:)<br>Also, the more power the manufacturer gives to the developers, the more power the developers will be able to pass on to the users in a user-friendly GUI.</p></htmltext>
<tokenext>It matters when you 're both .
That said , I avoided Android cause of its Java foundation and got a N900 .
have n't regretted it for a second : ) Also , the more power the manufacturer gives to the developers , the more power the developers will be able to pass on to the users in a user-friendly GUI .</tokentext>
<sentencetext>It matters when you're both.
That said, I avoided Android cause of its Java foundation and got a N900.
haven't regretted it for a second :)Also, the more power the manufacturer gives to the developers, the more power the developers will be able to pass on to the users in a user-friendly GUI.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31373266</id>
	<title>Re:3 Subjects That Make People Irrational</title>
	<author>Anonymous</author>
	<datestamp>1267815540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Politics<br>
Religion<br>
Linux Products</p></div><p>FTFY</p></div>
	</htmltext>
<tokenext>Politics Religion Linux ProductsFTFY</tokentext>
<sentencetext>Politics
Religion
Linux ProductsFTFY
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364622</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364092</id>
	<title>Re:Not as fast?</title>
	<author>Anonymous</author>
	<datestamp>1267703460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code?</i></p><p>Yes. All of them.</p><p>Whether you're allowed to is a different matter entirely.</p></htmltext>
<tokenext>Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code ? Yes .
All of them.Whether you 're allowed to is a different matter entirely .</tokentext>
<sentencetext>Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code?Yes.
All of them.Whether you're allowed to is a different matter entirely.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363766</id>
	<title>That's peachy</title>
	<author>Anonymous</author>
	<datestamp>1267702020000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Unfortunately right now it appears that for users it's the other way around.</p></htmltext>
<tokenext>Unfortunately right now it appears that for users it 's the other way around .</tokentext>
<sentencetext>Unfortunately right now it appears that for users it's the other way around.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368130</id>
	<title>Re:meh</title>
	<author>rdnetto</author>
	<datestamp>1267819380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I agree. Where's the article extolling the advantages of Maemo/Meego over Android?</p></htmltext>
<tokenext>I agree .
Where 's the article extolling the advantages of Maemo/Meego over Android ?</tokentext>
<sentencetext>I agree.
Where's the article extolling the advantages of Maemo/Meego over Android?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365076</id>
	<title>Re:Windows Mobile</title>
	<author>shutdown -p now</author>
	<datestamp>1267707900000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Then according to his logic, Windows Mobile is better than Android and iPhone combined, because not only can it run Java apps, but you can author software for it in practically any mainstream programming language.</p></div><p>I wouldn't be surprised if WinMo is actually the best platform, strictly from developer's perspective.</p></div>
	</htmltext>
<tokenext>Then according to his logic , Windows Mobile is better than Android and iPhone combined , because not only can it run Java apps , but you can author software for it in practically any mainstream programming language.I would n't be surprised if WinMo is actually the best platform , strictly from developer 's perspective .</tokentext>
<sentencetext>Then according to his logic, Windows Mobile is better than Android and iPhone combined, because not only can it run Java apps, but you can author software for it in practically any mainstream programming language.I wouldn't be surprised if WinMo is actually the best platform, strictly from developer's perspective.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364622</id>
	<title>3 Subjects That Make People Irrational</title>
	<author>Anonymous</author>
	<datestamp>1267705620000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Politics<br>Religion<br>Mac Products</htmltext>
<tokenext>PoliticsReligionMac Products</tokentext>
<sentencetext>PoliticsReligionMac Products</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31382622</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>rmadhuram</author>
	<datestamp>1267907700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How do you know? Any statistics to back this up? Chances are good that some of the apps on your iPhone *were* developed in one of the countries you mentioned.</htmltext>
<tokenext>How do you know ?
Any statistics to back this up ?
Chances are good that some of the apps on your iPhone * were * developed in one of the countries you mentioned .</tokentext>
<sentencetext>How do you know?
Any statistics to back this up?
Chances are good that some of the apps on your iPhone *were* developed in one of the countries you mentioned.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366234</id>
	<title>That's why Unix was written in Java</title>
	<author>gig</author>
	<datestamp>1267716180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you're a Java developer, of course Android's Java is great for you. But saying that is better than the C on the iPhone is ridiculous. The proof is in the pudding: the iPhone's apps are much deeper and sophisticated because in many cases they are 90\% desktop code, dropped in and create an interface.</p></htmltext>
<tokenext>If you 're a Java developer , of course Android 's Java is great for you .
But saying that is better than the C on the iPhone is ridiculous .
The proof is in the pudding : the iPhone 's apps are much deeper and sophisticated because in many cases they are 90 \ % desktop code , dropped in and create an interface .</tokentext>
<sentencetext>If you're a Java developer, of course Android's Java is great for you.
But saying that is better than the C on the iPhone is ridiculous.
The proof is in the pudding: the iPhone's apps are much deeper and sophisticated because in many cases they are 90\% desktop code, dropped in and create an interface.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365200</id>
	<title>Re:meh</title>
	<author>aliquis</author>
	<datestamp>1267708680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maemo is already dead, kinda.</p><p>It don't sounds like the N900 will get anything from Moblin and I guess future phones won't get Maemo so<nobr> <wbr></nobr>..</p><p><a href="http://moblin.org/" title="moblin.org" rel="nofollow">http://moblin.org/</a> [moblin.org]</p></htmltext>
<tokenext>Maemo is already dead , kinda.It do n't sounds like the N900 will get anything from Moblin and I guess future phones wo n't get Maemo so ..http : //moblin.org/ [ moblin.org ]</tokentext>
<sentencetext>Maemo is already dead, kinda.It don't sounds like the N900 will get anything from Moblin and I guess future phones won't get Maemo so ..http://moblin.org/ [moblin.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368250</id>
	<title>Re:No it will not</title>
	<author>Eric Smith</author>
	<datestamp>1267820760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Android has most of the standard Java classes other than AWT/Swing.  I was pleasantly surprised to find that it even has the Java reflection API.</htmltext>
<tokenext>Android has most of the standard Java classes other than AWT/Swing .
I was pleasantly surprised to find that it even has the Java reflection API .</tokentext>
<sentencetext>Android has most of the standard Java classes other than AWT/Swing.
I was pleasantly surprised to find that it even has the Java reflection API.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364842</id>
	<title>Nirvana Quest</title>
	<author>strangeattraction</author>
	<datestamp>1267706640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What the F@#ck I just just quit using Java to use Go. Can't Google make up it's mind. Ok, it is all quite clear now. It isn't the language that makes a product it is what you make with the language that is the product. That explains the popularity of the totally impure ObjectiveC. Infidels! calm restoring. Naval gaze.</htmltext>
<tokenext>What the F @ # ck I just just quit using Java to use Go .
Ca n't Google make up it 's mind .
Ok , it is all quite clear now .
It is n't the language that makes a product it is what you make with the language that is the product .
That explains the popularity of the totally impure ObjectiveC .
Infidels ! calm restoring .
Naval gaze .</tokentext>
<sentencetext>What the F@#ck I just just quit using Java to use Go.
Can't Google make up it's mind.
Ok, it is all quite clear now.
It isn't the language that makes a product it is what you make with the language that is the product.
That explains the popularity of the totally impure ObjectiveC.
Infidels! calm restoring.
Naval gaze.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365128</id>
	<title>Re:wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267708140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p><div class="quote"><p> Some of us carry smartphones to increase productivity, not play video games on a 4 inch screen.</p></div><p>And some people use smartphones to socialize and play games on a 4 inch screen.</p><p><div class="quote"><p>If you want to play games, buy one of those portable game widget things that Nintendo or Sony sells.</p></div><p>So, someone who already has a smartphone should spend potentially hundreds of dollars, and carry a separate device, rather than spending a few bucks for a game on a device they already own? Why, just because you don't approve of games on a phone out of some misguided ideological notions of purity and productivity?</p><p>Also, have you seen the relative difference in price for Nintendo DS and Sony PSP games versus the ones for the phones?</p></div>
	</htmltext>
<tokenext>Some of us carry smartphones to increase productivity , not play video games on a 4 inch screen.And some people use smartphones to socialize and play games on a 4 inch screen.If you want to play games , buy one of those portable game widget things that Nintendo or Sony sells.So , someone who already has a smartphone should spend potentially hundreds of dollars , and carry a separate device , rather than spending a few bucks for a game on a device they already own ?
Why , just because you do n't approve of games on a phone out of some misguided ideological notions of purity and productivity ? Also , have you seen the relative difference in price for Nintendo DS and Sony PSP games versus the ones for the phones ?</tokentext>
<sentencetext> Some of us carry smartphones to increase productivity, not play video games on a 4 inch screen.And some people use smartphones to socialize and play games on a 4 inch screen.If you want to play games, buy one of those portable game widget things that Nintendo or Sony sells.So, someone who already has a smartphone should spend potentially hundreds of dollars, and carry a separate device, rather than spending a few bucks for a game on a device they already own?
Why, just because you don't approve of games on a phone out of some misguided ideological notions of purity and productivity?Also, have you seen the relative difference in price for Nintendo DS and Sony PSP games versus the ones for the phones?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334</id>
	<title>Re:wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267704420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>Some of us carry smartphones to increase productivity, not play video games on a 4 inch screen.<br>If grand theft auto on your phone is a selling point... god help us all.<br>If you want to play games, buy one of those portable game widget things that Nintendo or Sony sells.</p></htmltext>
<tokenext>Some of us carry smartphones to increase productivity , not play video games on a 4 inch screen.If grand theft auto on your phone is a selling point... god help us all.If you want to play games , buy one of those portable game widget things that Nintendo or Sony sells .</tokentext>
<sentencetext>Some of us carry smartphones to increase productivity, not play video games on a 4 inch screen.If grand theft auto on your phone is a selling point... god help us all.If you want to play games, buy one of those portable game widget things that Nintendo or Sony sells.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364442</id>
	<title>The future is arriving faster every day.</title>
	<author>ErikZ</author>
	<datestamp>1267704840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>"...although it won't look pretty or run as fast as it does on multicore servers."</i></p><p>The Nexus One is multicore.</p></htmltext>
<tokenext>" ...although it wo n't look pretty or run as fast as it does on multicore servers .
" The Nexus One is multicore .</tokentext>
<sentencetext>"...although it won't look pretty or run as fast as it does on multicore servers.
"The Nexus One is multicore.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365614</id>
	<title>Why a free phone to someone who has one already?</title>
	<author>JSBiff</author>
	<datestamp>1267711440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That program doesn't seem to make a whole lot of sense to me. According to the article you linked to, you have to have *alread* created an app, put it on the market, gotten a good rating, and a lot of downloads. Stands to reason that if you have already developed a popular android market app, you must already have an android phone to test your app on? Why would you give a free phone to someone who already has one? What business benefit does that provide?</p><p>That sounds kind of like offering a free knife or pot to a professional chef, or maybe a free drill or reciprocating saw to a professional carpenter. They would already have their tools.</p><p>Giving free phones to developers who are not *yet* developing for the Android platform might make sense - say, giving them to interested iPhone developers to try to get them to port their apps to Android. Or perhaps to college students or other new programmers who code up some sort of app using the SDK emulator, but don't have a phone to test it on yet.</p></htmltext>
<tokenext>That program does n't seem to make a whole lot of sense to me .
According to the article you linked to , you have to have * alread * created an app , put it on the market , gotten a good rating , and a lot of downloads .
Stands to reason that if you have already developed a popular android market app , you must already have an android phone to test your app on ?
Why would you give a free phone to someone who already has one ?
What business benefit does that provide ? That sounds kind of like offering a free knife or pot to a professional chef , or maybe a free drill or reciprocating saw to a professional carpenter .
They would already have their tools.Giving free phones to developers who are not * yet * developing for the Android platform might make sense - say , giving them to interested iPhone developers to try to get them to port their apps to Android .
Or perhaps to college students or other new programmers who code up some sort of app using the SDK emulator , but do n't have a phone to test it on yet .</tokentext>
<sentencetext>That program doesn't seem to make a whole lot of sense to me.
According to the article you linked to, you have to have *alread* created an app, put it on the market, gotten a good rating, and a lot of downloads.
Stands to reason that if you have already developed a popular android market app, you must already have an android phone to test your app on?
Why would you give a free phone to someone who already has one?
What business benefit does that provide?That sounds kind of like offering a free knife or pot to a professional chef, or maybe a free drill or reciprocating saw to a professional carpenter.
They would already have their tools.Giving free phones to developers who are not *yet* developing for the Android platform might make sense - say, giving them to interested iPhone developers to try to get them to port their apps to Android.
Or perhaps to college students or other new programmers who code up some sort of app using the SDK emulator, but don't have a phone to test it on yet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364106</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798</id>
	<title>Thanks for Playing</title>
	<author>Anonymous</author>
	<datestamp>1267702200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext>"although it won't look pretty or run as fast...". That's all, Folks!</htmltext>
<tokenext>" although it wo n't look pretty or run as fast... " .
That 's all , Folks !</tokentext>
<sentencetext>"although it won't look pretty or run as fast...".
That's all, Folks!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368516</id>
	<title>!Java</title>
	<author>Skythe</author>
	<datestamp>1267781100000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>While Android is written in Java, the recommended way to program the GUI is using XML. That can be quite the stretch for someone that's never written a layout in XML (read: myself).</htmltext>
<tokenext>While Android is written in Java , the recommended way to program the GUI is using XML .
That can be quite the stretch for someone that 's never written a layout in XML ( read : myself ) .</tokentext>
<sentencetext>While Android is written in Java, the recommended way to program the GUI is using XML.
That can be quite the stretch for someone that's never written a layout in XML (read: myself).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364726</id>
	<title>Said this Months Ago And Got Flamed</title>
	<author>curmudgeon99</author>
	<datestamp>1267706040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How curious. Right here on Slashdot I said this exact thing--months ago--and I got flamed without mercy. My reasons? The unpredictable nature of the iPhone app acceptance and then Java.</htmltext>
<tokenext>How curious .
Right here on Slashdot I said this exact thing--months ago--and I got flamed without mercy .
My reasons ?
The unpredictable nature of the iPhone app acceptance and then Java .</tokentext>
<sentencetext>How curious.
Right here on Slashdot I said this exact thing--months ago--and I got flamed without mercy.
My reasons?
The unpredictable nature of the iPhone app acceptance and then Java.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365216</id>
	<title>Re:wake me up when it catches up</title>
	<author>UseCase</author>
	<datestamp>1267708800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yep.  Lots of us tech heads forget that its about the users.  I don't have a problem developing for iPhone or Android.  I just following the money/users.  I want to put products out that people outside of my peer group will use.</htmltext>
<tokenext>Yep .
Lots of us tech heads forget that its about the users .
I do n't have a problem developing for iPhone or Android .
I just following the money/users .
I want to put products out that people outside of my peer group will use .</tokentext>
<sentencetext>Yep.
Lots of us tech heads forget that its about the users.
I don't have a problem developing for iPhone or Android.
I just following the money/users.
I want to put products out that people outside of my peer group will use.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367252</id>
	<title>Re:No it will not</title>
	<author>hunangarden</author>
	<datestamp>1267723980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Android does not use swing or awt. It has its on UI model. It works pretty well and is easier to work with than swing or awt. Layouts can be done using a WYSIWYG interface and hand edited as needed (its in XML).</p><p>You can use many of the standard java jdk classes (java.lang, java.util, java.net, java.math, java.sql, etc, etc), but sure you will have to learn some of the android specific libraries as well.</p><p>In general programming with Android is pretty easy for experienced Java programmers. But there is certainly some learning curve to get started.</p></htmltext>
<tokenext>Android does not use swing or awt .
It has its on UI model .
It works pretty well and is easier to work with than swing or awt .
Layouts can be done using a WYSIWYG interface and hand edited as needed ( its in XML ) .You can use many of the standard java jdk classes ( java.lang , java.util , java.net , java.math , java.sql , etc , etc ) , but sure you will have to learn some of the android specific libraries as well.In general programming with Android is pretty easy for experienced Java programmers .
But there is certainly some learning curve to get started .</tokentext>
<sentencetext>Android does not use swing or awt.
It has its on UI model.
It works pretty well and is easier to work with than swing or awt.
Layouts can be done using a WYSIWYG interface and hand edited as needed (its in XML).You can use many of the standard java jdk classes (java.lang, java.util, java.net, java.math, java.sql, etc, etc), but sure you will have to learn some of the android specific libraries as well.In general programming with Android is pretty easy for experienced Java programmers.
But there is certainly some learning curve to get started.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367906</id>
	<title>The public prefers a huge app store to DRM rants</title>
	<author>judeancodersfront</author>
	<datestamp>1267730220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>and would only be interested in jailbreaking if it was a movie that starred Matt Damon.

Developers like the app store, users like the app store, and what you don't like really doesn't matter to either group.</htmltext>
<tokenext>and would only be interested in jailbreaking if it was a movie that starred Matt Damon .
Developers like the app store , users like the app store , and what you do n't like really does n't matter to either group .</tokentext>
<sentencetext>and would only be interested in jailbreaking if it was a movie that starred Matt Damon.
Developers like the app store, users like the app store, and what you don't like really doesn't matter to either group.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644</id>
	<title>When will we learn...</title>
	<author>BearRanger</author>
	<datestamp>1267705680000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>That a phone that caters to developers is NOT a phone that the rest of the world has much interest in using.  I love the flexibility promised by Android, but if smartphones are going to take over the world I would not want my grandmother to have to deal with fragmentation and software complexity.  Android phones and the iPhone occupy two different market niches.  This is a good thing for both developers and consumers.</htmltext>
<tokenext>That a phone that caters to developers is NOT a phone that the rest of the world has much interest in using .
I love the flexibility promised by Android , but if smartphones are going to take over the world I would not want my grandmother to have to deal with fragmentation and software complexity .
Android phones and the iPhone occupy two different market niches .
This is a good thing for both developers and consumers .</tokentext>
<sentencetext>That a phone that caters to developers is NOT a phone that the rest of the world has much interest in using.
I love the flexibility promised by Android, but if smartphones are going to take over the world I would not want my grandmother to have to deal with fragmentation and software complexity.
Android phones and the iPhone occupy two different market niches.
This is a good thing for both developers and consumers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367178</id>
	<title>Android can byte my shiny metal</title>
	<author>Anonymous</author>
	<datestamp>1267723500000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>I develop a fairly major app for iPhone, BlackBerry and Android.</p><p>As a developer that likes to tinker, the lack of root access to the iPhone offends me.  It is like selling a fast car with a governor that limits you to 55 mph.  The draconian signing certificates and provisioning profiles can be very frustrating.  And the simulator SDK (not the simulator itself) is incompatible with iPhone development, which is ridiculous.  That is to say, there are headers and libraries supported on the simulator but not the hardware, like someone might choose the simulator as a final release platform.</p><p>But that is about it.  I have a few significant complaints about developing for the iPhone.  None crop up on a daily basis.  There are many enjoyable aspects about the iPhone.  The hardware is consistent and reliable.  The IDE is consistent and reliable.  The device is responsive and predictable.</p><p>Compare that to Android and Blackberry, where dealing with the IDE, simulator and hardware are a daily ordeal.  Java is slow.  Eclipse is buggy.  In the car metaphor, these things top out at 55 full throttle.  And the idea that you have full access to a system from Java is kind of a joke.  Android has done away with the application metaphor in favor of the Activity.  The openness of Android seems really cool and will probably end up like the security nightmare that is IE6.</p><p>And can I just say that the Android naming conventions are painfully stupid.  Everything has a catchy thesaurus name that bears little relation to the actual functionality.  They may have cured my of my own anal naming conventions.  Activity, Intent, Parcel, Arghh.  Apple names are wordy, ugly, straight forward and very informative.</p><p>The documentation for all 3 is fairly weak.  Apple dictates who can say what about everything, but even with that it is often easier to find helpful search results on iPhone related problems.  I would say that Android wins for documentation overall.</p><p>Overall, developing on the iPhone is nowhere near as painful as Android or BlackBerry.  The initial role out is worse on iPhone, but the daily grind is not nearly as bad.  I kind of lumped Android and Blackberry together there, but Blackberry is really much worse than Android.</p><p>And the article mentions using existing Java code on Android.  We ported from BlackBerry to Android and maybe 1\% of the actual code made it across untouched.  You would think, moving from one Java smartphone to another Java smartphone, that anything at all might share some commonality.  But no.  Even the core classes for arrays and maps are different.  Only the strings survived.</p></htmltext>
<tokenext>I develop a fairly major app for iPhone , BlackBerry and Android.As a developer that likes to tinker , the lack of root access to the iPhone offends me .
It is like selling a fast car with a governor that limits you to 55 mph .
The draconian signing certificates and provisioning profiles can be very frustrating .
And the simulator SDK ( not the simulator itself ) is incompatible with iPhone development , which is ridiculous .
That is to say , there are headers and libraries supported on the simulator but not the hardware , like someone might choose the simulator as a final release platform.But that is about it .
I have a few significant complaints about developing for the iPhone .
None crop up on a daily basis .
There are many enjoyable aspects about the iPhone .
The hardware is consistent and reliable .
The IDE is consistent and reliable .
The device is responsive and predictable.Compare that to Android and Blackberry , where dealing with the IDE , simulator and hardware are a daily ordeal .
Java is slow .
Eclipse is buggy .
In the car metaphor , these things top out at 55 full throttle .
And the idea that you have full access to a system from Java is kind of a joke .
Android has done away with the application metaphor in favor of the Activity .
The openness of Android seems really cool and will probably end up like the security nightmare that is IE6.And can I just say that the Android naming conventions are painfully stupid .
Everything has a catchy thesaurus name that bears little relation to the actual functionality .
They may have cured my of my own anal naming conventions .
Activity , Intent , Parcel , Arghh .
Apple names are wordy , ugly , straight forward and very informative.The documentation for all 3 is fairly weak .
Apple dictates who can say what about everything , but even with that it is often easier to find helpful search results on iPhone related problems .
I would say that Android wins for documentation overall.Overall , developing on the iPhone is nowhere near as painful as Android or BlackBerry .
The initial role out is worse on iPhone , but the daily grind is not nearly as bad .
I kind of lumped Android and Blackberry together there , but Blackberry is really much worse than Android.And the article mentions using existing Java code on Android .
We ported from BlackBerry to Android and maybe 1 \ % of the actual code made it across untouched .
You would think , moving from one Java smartphone to another Java smartphone , that anything at all might share some commonality .
But no .
Even the core classes for arrays and maps are different .
Only the strings survived .</tokentext>
<sentencetext>I develop a fairly major app for iPhone, BlackBerry and Android.As a developer that likes to tinker, the lack of root access to the iPhone offends me.
It is like selling a fast car with a governor that limits you to 55 mph.
The draconian signing certificates and provisioning profiles can be very frustrating.
And the simulator SDK (not the simulator itself) is incompatible with iPhone development, which is ridiculous.
That is to say, there are headers and libraries supported on the simulator but not the hardware, like someone might choose the simulator as a final release platform.But that is about it.
I have a few significant complaints about developing for the iPhone.
None crop up on a daily basis.
There are many enjoyable aspects about the iPhone.
The hardware is consistent and reliable.
The IDE is consistent and reliable.
The device is responsive and predictable.Compare that to Android and Blackberry, where dealing with the IDE, simulator and hardware are a daily ordeal.
Java is slow.
Eclipse is buggy.
In the car metaphor, these things top out at 55 full throttle.
And the idea that you have full access to a system from Java is kind of a joke.
Android has done away with the application metaphor in favor of the Activity.
The openness of Android seems really cool and will probably end up like the security nightmare that is IE6.And can I just say that the Android naming conventions are painfully stupid.
Everything has a catchy thesaurus name that bears little relation to the actual functionality.
They may have cured my of my own anal naming conventions.
Activity, Intent, Parcel, Arghh.
Apple names are wordy, ugly, straight forward and very informative.The documentation for all 3 is fairly weak.
Apple dictates who can say what about everything, but even with that it is often easier to find helpful search results on iPhone related problems.
I would say that Android wins for documentation overall.Overall, developing on the iPhone is nowhere near as painful as Android or BlackBerry.
The initial role out is worse on iPhone, but the daily grind is not nearly as bad.
I kind of lumped Android and Blackberry together there, but Blackberry is really much worse than Android.And the article mentions using existing Java code on Android.
We ported from BlackBerry to Android and maybe 1\% of the actual code made it across untouched.
You would think, moving from one Java smartphone to another Java smartphone, that anything at all might share some commonality.
But no.
Even the core classes for arrays and maps are different.
Only the strings survived.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364108</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>Anonymous</author>
	<datestamp>1267703520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Thank God those stupid Asian guys aren't as clever as us white folks, eh?</p></htmltext>
<tokenext>Thank God those stupid Asian guys are n't as clever as us white folks , eh ?</tokentext>
<sentencetext>Thank God those stupid Asian guys aren't as clever as us white folks, eh?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364262</id>
	<title>Re:No it will not</title>
	<author>Tapewolf</author>
	<datestamp>1267704120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The UI and the program entry point have to be written in Java.  However, since it supports JNI, you can reuse all the program logic from C/C++, assuming you haven't stuffed it full of win32-specific stuff.</htmltext>
<tokenext>The UI and the program entry point have to be written in Java .
However , since it supports JNI , you can reuse all the program logic from C/C + + , assuming you have n't stuffed it full of win32-specific stuff .</tokentext>
<sentencetext>The UI and the program entry point have to be written in Java.
However, since it supports JNI, you can reuse all the program logic from C/C++, assuming you haven't stuffed it full of win32-specific stuff.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363998</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367446</id>
	<title>Re:Use "em" not "px" when defining the UI</title>
	<author>Idiomatick</author>
	<datestamp>1267725420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>"Incidentally bitmaps that use em have not been invented yet." Huh?.... Set the 50x50px image to be 12x12em<nobr> <wbr></nobr>.... works fine on the interwebs.<br> <br>Basically speaking we can make websites that look good, perfectly fine when dealing with tons of different screens, resolutions and DPI. No reason why aps wouldn't work. YES, it makes it harder. You have to think about it a bit. Bit it is pretty fucking minor. Look at ALLLLLL windows aps. You can resize them freely within certain bounds and they don't fuck up horribly. So it seems like we've been doing this for decades.</htmltext>
<tokenext>" Incidentally bitmaps that use em have not been invented yet .
" Huh ? ... .
Set the 50x50px image to be 12x12em .... works fine on the interwebs .
Basically speaking we can make websites that look good , perfectly fine when dealing with tons of different screens , resolutions and DPI .
No reason why aps would n't work .
YES , it makes it harder .
You have to think about it a bit .
Bit it is pretty fucking minor .
Look at ALLLLLL windows aps .
You can resize them freely within certain bounds and they do n't fuck up horribly .
So it seems like we 've been doing this for decades .</tokentext>
<sentencetext>"Incidentally bitmaps that use em have not been invented yet.
" Huh?....
Set the 50x50px image to be 12x12em .... works fine on the interwebs.
Basically speaking we can make websites that look good, perfectly fine when dealing with tons of different screens, resolutions and DPI.
No reason why aps wouldn't work.
YES, it makes it harder.
You have to think about it a bit.
Bit it is pretty fucking minor.
Look at ALLLLLL windows aps.
You can resize them freely within certain bounds and they don't fuck up horribly.
So it seems like we've been doing this for decades.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364674</id>
	<title>NOT a full comparison.</title>
	<author>MrCrassic</author>
	<datestamp>1267705860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don't know enough about Android to really comment on other aspects of usability, but this article mainly compares development between both platforms. To be frank, though, I don't think the Android Alliance had to do a lot to be better than a system that only allows developers to code on OS X with a language that's almost entirely bound to that platform and under the control of an authoritarian and seemingly draconian submission control system.</p><p>However, under the Android platform gains critical mass (which the Droid and the Nexus One, to a lesser extent, are trying to do), the best bet to gaining lots of visibility and/or profit is by developing for the iPhone.<br>The article is pretty comprehensive; I recommend it. (Probably means nothing here on<nobr> <wbr></nobr>/. though.<nobr> <wbr></nobr>:p)</p></htmltext>
<tokenext>I do n't know enough about Android to really comment on other aspects of usability , but this article mainly compares development between both platforms .
To be frank , though , I do n't think the Android Alliance had to do a lot to be better than a system that only allows developers to code on OS X with a language that 's almost entirely bound to that platform and under the control of an authoritarian and seemingly draconian submission control system.However , under the Android platform gains critical mass ( which the Droid and the Nexus One , to a lesser extent , are trying to do ) , the best bet to gaining lots of visibility and/or profit is by developing for the iPhone.The article is pretty comprehensive ; I recommend it .
( Probably means nothing here on / .
though. : p )</tokentext>
<sentencetext>I don't know enough about Android to really comment on other aspects of usability, but this article mainly compares development between both platforms.
To be frank, though, I don't think the Android Alliance had to do a lot to be better than a system that only allows developers to code on OS X with a language that's almost entirely bound to that platform and under the control of an authoritarian and seemingly draconian submission control system.However, under the Android platform gains critical mass (which the Droid and the Nexus One, to a lesser extent, are trying to do), the best bet to gaining lots of visibility and/or profit is by developing for the iPhone.The article is pretty comprehensive; I recommend it.
(Probably means nothing here on /.
though. :p)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31400626</id>
	<title>Screen Resolution Issue Debunked for the /. Posers</title>
	<author>salesgeek</author>
	<datestamp>1268064000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What a bunch of dip-shiat posers.  <b>First, Android apps are run on a virtual machine</b> (yes, that's right, even on the phone). If you've actually cut code for Android, you would probably be familiar with the build/test cycle which consists of compiling and running on an Android Virual Device (AVD - an emulator that lets you simulate different phone configs) which comes with the SDK. <b>The emulator supports multiple resolutions</b> as well as multiple versions of the Android OS.  Screen resolutions are really not that much of a challenge.  Funky hardware (say, a totally bizarre, non-standard GPS chip) might be, but I have yet to run into a situation where the Android SDK doesn't provide an abstraction that just takes care of it for app development.</p><p>Here's a link to the <a href="http://developer.android.com/guide/practices/screens\_support.html" title="android.com">Android developer documentation on the multiple screen resolutions</a> [android.com].  It just isn't that tough, and anyone who says multiple screen resolutions are either has never cut code for Android or simply is incapable of reading the manual.</p><p>Note to Mr. Buy A Lot of Hardware: Your code does not know the difference between being inside an AVD or running on a real phone.  I think someone at your company has a fetish for gadgets and is tickling it at your expense.</p><p><b>Note to<nobr> <wbr></nobr>/. at large:RTFM</b> before opening mouth, RTFM and you'll be amazed what you learn.  For the n00bs: RTFM = Read The Fscking Manual.  More for the n00bs: typing $man fsck is not what RTFM wants you to do.</p><p>Ironically Android has been designed to provide developers a way to write one application that can be supported by many devices. It's also open source, and the SDK (and built in emulator) is freely available.  This means if you want to be an <b>expert</b> on Android, you can download the SDK, and EVEN WITHOUT OWNING AN ANDROID PHONE write your very own applications... or try to or whatever.  Just stop acting like you know what you are doing or you are some mobile software development expert when you don't even know what some guy who just installed the SDK knows about 15 minutes into trying out the SDK.  Sheesh.<nobr> <wbr></nobr>// Feel Better Now<br>/<nobr> <wbr></nobr>/. continues to be<nobr> <wbr></nobr>/.</p></htmltext>
<tokenext>What a bunch of dip-shiat posers .
First , Android apps are run on a virtual machine ( yes , that 's right , even on the phone ) .
If you 've actually cut code for Android , you would probably be familiar with the build/test cycle which consists of compiling and running on an Android Virual Device ( AVD - an emulator that lets you simulate different phone configs ) which comes with the SDK .
The emulator supports multiple resolutions as well as multiple versions of the Android OS .
Screen resolutions are really not that much of a challenge .
Funky hardware ( say , a totally bizarre , non-standard GPS chip ) might be , but I have yet to run into a situation where the Android SDK does n't provide an abstraction that just takes care of it for app development.Here 's a link to the Android developer documentation on the multiple screen resolutions [ android.com ] .
It just is n't that tough , and anyone who says multiple screen resolutions are either has never cut code for Android or simply is incapable of reading the manual.Note to Mr. Buy A Lot of Hardware : Your code does not know the difference between being inside an AVD or running on a real phone .
I think someone at your company has a fetish for gadgets and is tickling it at your expense.Note to / .
at large : RTFM before opening mouth , RTFM and you 'll be amazed what you learn .
For the n00bs : RTFM = Read The Fscking Manual .
More for the n00bs : typing $ man fsck is not what RTFM wants you to do.Ironically Android has been designed to provide developers a way to write one application that can be supported by many devices .
It 's also open source , and the SDK ( and built in emulator ) is freely available .
This means if you want to be an expert on Android , you can download the SDK , and EVEN WITHOUT OWNING AN ANDROID PHONE write your very own applications... or try to or whatever .
Just stop acting like you know what you are doing or you are some mobile software development expert when you do n't even know what some guy who just installed the SDK knows about 15 minutes into trying out the SDK .
Sheesh. // Feel Better Now/ / .
continues to be / .</tokentext>
<sentencetext>What a bunch of dip-shiat posers.
First, Android apps are run on a virtual machine (yes, that's right, even on the phone).
If you've actually cut code for Android, you would probably be familiar with the build/test cycle which consists of compiling and running on an Android Virual Device (AVD - an emulator that lets you simulate different phone configs) which comes with the SDK.
The emulator supports multiple resolutions as well as multiple versions of the Android OS.
Screen resolutions are really not that much of a challenge.
Funky hardware (say, a totally bizarre, non-standard GPS chip) might be, but I have yet to run into a situation where the Android SDK doesn't provide an abstraction that just takes care of it for app development.Here's a link to the Android developer documentation on the multiple screen resolutions [android.com].
It just isn't that tough, and anyone who says multiple screen resolutions are either has never cut code for Android or simply is incapable of reading the manual.Note to Mr. Buy A Lot of Hardware: Your code does not know the difference between being inside an AVD or running on a real phone.
I think someone at your company has a fetish for gadgets and is tickling it at your expense.Note to /.
at large:RTFM before opening mouth, RTFM and you'll be amazed what you learn.
For the n00bs: RTFM = Read The Fscking Manual.
More for the n00bs: typing $man fsck is not what RTFM wants you to do.Ironically Android has been designed to provide developers a way to write one application that can be supported by many devices.
It's also open source, and the SDK (and built in emulator) is freely available.
This means if you want to be an expert on Android, you can download the SDK, and EVEN WITHOUT OWNING AN ANDROID PHONE write your very own applications... or try to or whatever.
Just stop acting like you know what you are doing or you are some mobile software development expert when you don't even know what some guy who just installed the SDK knows about 15 minutes into trying out the SDK.
Sheesh. // Feel Better Now/ /.
continues to be /.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366608</id>
	<title>Security</title>
	<author>beaverbrother</author>
	<datestamp>1267719540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Is anyone else worried about viruses on Android? While I'm sure apple doesn't go too far to vet security, Google doesn't really examine Android apps much at all. I wouldn't be surprised if trojans, etc get distributed through the Android marketplace in the near future</htmltext>
<tokenext>Is anyone else worried about viruses on Android ?
While I 'm sure apple does n't go too far to vet security , Google does n't really examine Android apps much at all .
I would n't be surprised if trojans , etc get distributed through the Android marketplace in the near future</tokentext>
<sentencetext>Is anyone else worried about viruses on Android?
While I'm sure apple doesn't go too far to vet security, Google doesn't really examine Android apps much at all.
I wouldn't be surprised if trojans, etc get distributed through the Android marketplace in the near future</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364420</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>Locke2005</author>
	<datestamp>1267704840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Wow! You've actually used 99\% of the iPhone apps?!? You must have a lot of spare time on your hands!</htmltext>
<tokenext>Wow !
You 've actually used 99 \ % of the iPhone apps ? ! ?
You must have a lot of spare time on your hands !</tokentext>
<sentencetext>Wow!
You've actually used 99\% of the iPhone apps?!?
You must have a lot of spare time on your hands!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369982</id>
	<title>It's all about the killer apps</title>
	<author>Fastfwd</author>
	<datestamp>1267798740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Making it easy for developers is not the key. Attracting the developers on key strategic apps is it. The number of apps in your store does not matter if you don't have the 5-10 apps that the user wants/needs.</p><p>I think that both Apple and Android have an app store that covers the needs of most users but the Apple store is still the most attractive right now. I have not browsed both extensively so at this point it's just the word to mouth about what I can or cannot do with the phone that would sell me on the iPhone.</p></htmltext>
<tokenext>Making it easy for developers is not the key .
Attracting the developers on key strategic apps is it .
The number of apps in your store does not matter if you do n't have the 5-10 apps that the user wants/needs.I think that both Apple and Android have an app store that covers the needs of most users but the Apple store is still the most attractive right now .
I have not browsed both extensively so at this point it 's just the word to mouth about what I can or can not do with the phone that would sell me on the iPhone .</tokentext>
<sentencetext>Making it easy for developers is not the key.
Attracting the developers on key strategic apps is it.
The number of apps in your store does not matter if you don't have the 5-10 apps that the user wants/needs.I think that both Apple and Android have an app store that covers the needs of most users but the Apple store is still the most attractive right now.
I have not browsed both extensively so at this point it's just the word to mouth about what I can or cannot do with the phone that would sell me on the iPhone.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</id>
	<title>meh</title>
	<author>LiquidCoooled</author>
	<datestamp>1267702200000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>iphone and android aren't really inclusive.<br>open source is meant to be about choice and freedom.</p><p>the nokia n900 + maemo allows multiple languages and frameworks (x11 gtk qt sdl gles and whatever else you can throw at it) to peacefully coexist together<nobr> <wbr></nobr>:)</p><p>don't take my word for it though, i'm biased</p></htmltext>
<tokenext>iphone and android are n't really inclusive.open source is meant to be about choice and freedom.the nokia n900 + maemo allows multiple languages and frameworks ( x11 gtk qt sdl gles and whatever else you can throw at it ) to peacefully coexist together : ) do n't take my word for it though , i 'm biased</tokentext>
<sentencetext>iphone and android aren't really inclusive.open source is meant to be about choice and freedom.the nokia n900 + maemo allows multiple languages and frameworks (x11 gtk qt sdl gles and whatever else you can throw at it) to peacefully coexist together :)don't take my word for it though, i'm biased</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365334</id>
	<title>iPhone is also UNIX.</title>
	<author>flyhigher</author>
	<datestamp>1267709520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket,' Wayner writes".</p><p>Except that the iPhone is also "really a UNIX machine you can slip into your pocket.</p><p><a href="http://www.servin.com/iphone/iPhone-Unix-System-Calls.html" title="servin.com" rel="nofollow">http://www.servin.com/iphone/iPhone-Unix-System-Calls.html</a> [servin.com]</p></htmltext>
<tokenext>" a number of Android applications are offering practical solutions that unlock the power of a phone that 's really a Unix machine you can slip into your pocket, ' Wayner writes " .Except that the iPhone is also " really a UNIX machine you can slip into your pocket.http : //www.servin.com/iphone/iPhone-Unix-System-Calls.html [ servin.com ]</tokentext>
<sentencetext>"a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket,' Wayner writes".Except that the iPhone is also "really a UNIX machine you can slip into your pocket.http://www.servin.com/iphone/iPhone-Unix-System-Calls.html [servin.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364440</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>EastCoastSurfer</author>
	<datestamp>1267704840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Haha.  If you know C and have an idea about OO concepts then obj-c is just as easy to learn as anything else.  Many (most? all?) C libraries that don't rely on graphics should work just fine on the iPhone.  Maybe it's C that's too hard for people to learn?</p></htmltext>
<tokenext>Haha .
If you know C and have an idea about OO concepts then obj-c is just as easy to learn as anything else .
Many ( most ?
all ? ) C libraries that do n't rely on graphics should work just fine on the iPhone .
Maybe it 's C that 's too hard for people to learn ?</tokentext>
<sentencetext>Haha.
If you know C and have an idea about OO concepts then obj-c is just as easy to learn as anything else.
Many (most?
all?) C libraries that don't rely on graphics should work just fine on the iPhone.
Maybe it's C that's too hard for people to learn?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930</id>
	<title>Not as fast?</title>
	<author>Anonymous</author>
	<datestamp>1267702740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>From TFA<br><i>code from other Java programs will run on your Android phone -- although it won't look pretty or run as fast as it does on multicore servers</i> </p><p>I'm not a developer but once of the criticisms I see constantly leveled against Java is how slow it is.  Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code?</p></htmltext>
<tokenext>From TFAcode from other Java programs will run on your Android phone -- although it wo n't look pretty or run as fast as it does on multicore servers I 'm not a developer but once of the criticisms I see constantly leveled against Java is how slow it is .
Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code ?</tokentext>
<sentencetext>From TFAcode from other Java programs will run on your Android phone -- although it won't look pretty or run as fast as it does on multicore servers I'm not a developer but once of the criticisms I see constantly leveled against Java is how slow it is.
Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369532</id>
	<title>Re:Java as an "advantage?"</title>
	<author>Xest</author>
	<datestamp>1267794120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Objective-C has advantages, such as that it is compiled."</p><p>Huh? Java is compiled too, but it's JIT compilation which is better in that it allows optimisation for the specific device on which it is being run, not the generic platform on which it is expected to be run. The claim that Objective-C being compiled is an advantage makes no sense at all. The rest of that paragraph seems to be based on the false premise that Java is inherently slower than Objective-C which just simply isn't true.</p><p>"X-Code is a purpose-built, clean-sheet IDE that may lack a few power features found in Eclipse, and Eclipse has numerous plug-ins, but Eclipse also has a pretty diabolical UI, especially compared to software from Apple."</p><p>I do agree, I'm not a fan of Eclipse, but then, Apple's software doesn't come close to beating Visual Studio, so in this respect it's really Windows Mobile that has the IDE advantage of any platform. It's a shame really there's no official support for NetBeans rather than Eclipse for Android, NetBeans is IMHO, much better.</p><p>"Java, Eclipse, and the other Android SDK tools are more than good enough, but they are not a big advantage, or, depending on your tastes, any advantage. There is a rough equivalence here that will probably extend to Android doing for client Java what iPhone did for Objective-C - making it popular. That is, Android apps will probably be the most common form of interactive client Java apps, if they have not already eclipsed AWT, Swing, SWT, and other Java UI libraries."</p><p>I'm not sure you know too much about Java, but it's far and away the most commonly used language across the globe and has been for many many years. Android is small fry in terms of overall Java development, even on the client side. When you go into a Doctor's surgery to book your appointment, use a system to pickup your prepaid Cinema or Airline tickets, get served by someone at checkout, the chances are these systems are all client side Java. Even on the desktop there are some prominent Java apps- Vuze (Azureus) is a popular BitTorrent client for example that has a pretty nice interface.</p><p>Regarding iPhone books as Amazon top sellers, it's also not really a meaningful metric (although I just had a look myself, and it doesn't even seem to be true- are you sure you weren't looking at your recommendations?). This could simply because Android has great online documentation for example.</p><p>Java certainly is an advantage, if not only because it's prominence as a language and portability between Windows, Linux, Mac, Android phones, Blackberrys, Unix and so forth means that even if you have to write the UI, you don't have to re-write the libraries. As pointed out above, it's not as if performance is an issue in Java either, see here, and keep in mind this page is now 6 years old:</p><p><a href="http://www.idiom.com/~zilla/Computer/javaCbenchmark.html" title="idiom.com">http://www.idiom.com/~zilla/Computer/javaCbenchmark.html</a> [idiom.com]</p><p>The only thing Java really does need is IDE improvements, if NetBeans or Eclipse were taken up to the quality and usefulness of Visual Studio then that'd be awesome.</p></htmltext>
<tokenext>" Objective-C has advantages , such as that it is compiled. " Huh ?
Java is compiled too , but it 's JIT compilation which is better in that it allows optimisation for the specific device on which it is being run , not the generic platform on which it is expected to be run .
The claim that Objective-C being compiled is an advantage makes no sense at all .
The rest of that paragraph seems to be based on the false premise that Java is inherently slower than Objective-C which just simply is n't true .
" X-Code is a purpose-built , clean-sheet IDE that may lack a few power features found in Eclipse , and Eclipse has numerous plug-ins , but Eclipse also has a pretty diabolical UI , especially compared to software from Apple .
" I do agree , I 'm not a fan of Eclipse , but then , Apple 's software does n't come close to beating Visual Studio , so in this respect it 's really Windows Mobile that has the IDE advantage of any platform .
It 's a shame really there 's no official support for NetBeans rather than Eclipse for Android , NetBeans is IMHO , much better .
" Java , Eclipse , and the other Android SDK tools are more than good enough , but they are not a big advantage , or , depending on your tastes , any advantage .
There is a rough equivalence here that will probably extend to Android doing for client Java what iPhone did for Objective-C - making it popular .
That is , Android apps will probably be the most common form of interactive client Java apps , if they have not already eclipsed AWT , Swing , SWT , and other Java UI libraries .
" I 'm not sure you know too much about Java , but it 's far and away the most commonly used language across the globe and has been for many many years .
Android is small fry in terms of overall Java development , even on the client side .
When you go into a Doctor 's surgery to book your appointment , use a system to pickup your prepaid Cinema or Airline tickets , get served by someone at checkout , the chances are these systems are all client side Java .
Even on the desktop there are some prominent Java apps- Vuze ( Azureus ) is a popular BitTorrent client for example that has a pretty nice interface.Regarding iPhone books as Amazon top sellers , it 's also not really a meaningful metric ( although I just had a look myself , and it does n't even seem to be true- are you sure you were n't looking at your recommendations ? ) .
This could simply because Android has great online documentation for example.Java certainly is an advantage , if not only because it 's prominence as a language and portability between Windows , Linux , Mac , Android phones , Blackberrys , Unix and so forth means that even if you have to write the UI , you do n't have to re-write the libraries .
As pointed out above , it 's not as if performance is an issue in Java either , see here , and keep in mind this page is now 6 years old : http : //www.idiom.com/ ~ zilla/Computer/javaCbenchmark.html [ idiom.com ] The only thing Java really does need is IDE improvements , if NetBeans or Eclipse were taken up to the quality and usefulness of Visual Studio then that 'd be awesome .</tokentext>
<sentencetext>"Objective-C has advantages, such as that it is compiled."Huh?
Java is compiled too, but it's JIT compilation which is better in that it allows optimisation for the specific device on which it is being run, not the generic platform on which it is expected to be run.
The claim that Objective-C being compiled is an advantage makes no sense at all.
The rest of that paragraph seems to be based on the false premise that Java is inherently slower than Objective-C which just simply isn't true.
"X-Code is a purpose-built, clean-sheet IDE that may lack a few power features found in Eclipse, and Eclipse has numerous plug-ins, but Eclipse also has a pretty diabolical UI, especially compared to software from Apple.
"I do agree, I'm not a fan of Eclipse, but then, Apple's software doesn't come close to beating Visual Studio, so in this respect it's really Windows Mobile that has the IDE advantage of any platform.
It's a shame really there's no official support for NetBeans rather than Eclipse for Android, NetBeans is IMHO, much better.
"Java, Eclipse, and the other Android SDK tools are more than good enough, but they are not a big advantage, or, depending on your tastes, any advantage.
There is a rough equivalence here that will probably extend to Android doing for client Java what iPhone did for Objective-C - making it popular.
That is, Android apps will probably be the most common form of interactive client Java apps, if they have not already eclipsed AWT, Swing, SWT, and other Java UI libraries.
"I'm not sure you know too much about Java, but it's far and away the most commonly used language across the globe and has been for many many years.
Android is small fry in terms of overall Java development, even on the client side.
When you go into a Doctor's surgery to book your appointment, use a system to pickup your prepaid Cinema or Airline tickets, get served by someone at checkout, the chances are these systems are all client side Java.
Even on the desktop there are some prominent Java apps- Vuze (Azureus) is a popular BitTorrent client for example that has a pretty nice interface.Regarding iPhone books as Amazon top sellers, it's also not really a meaningful metric (although I just had a look myself, and it doesn't even seem to be true- are you sure you weren't looking at your recommendations?).
This could simply because Android has great online documentation for example.Java certainly is an advantage, if not only because it's prominence as a language and portability between Windows, Linux, Mac, Android phones, Blackberrys, Unix and so forth means that even if you have to write the UI, you don't have to re-write the libraries.
As pointed out above, it's not as if performance is an issue in Java either, see here, and keep in mind this page is now 6 years old:http://www.idiom.com/~zilla/Computer/javaCbenchmark.html [idiom.com]The only thing Java really does need is IDE improvements, if NetBeans or Eclipse were taken up to the quality and usefulness of Visual Studio then that'd be awesome.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369332</id>
	<title>Re:Not as fast?</title>
	<author>Xest</author>
	<datestamp>1267791480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Read what it says again- it's not saying that Java is slow, it's just pointing out that apps wont run as fast on a phone as they do on multicore servers, because phones have much lower performance hardware.</p><p>Java in terms of speed is fine, it's as fast as C++ apps in the overwhelming majority of cases, and often even faster due to being able to optimise for the specific system the code is being executed on, rather than having to optimise for the general case as C++ compilers have to do.</p></htmltext>
<tokenext>Read what it says again- it 's not saying that Java is slow , it 's just pointing out that apps wont run as fast on a phone as they do on multicore servers , because phones have much lower performance hardware.Java in terms of speed is fine , it 's as fast as C + + apps in the overwhelming majority of cases , and often even faster due to being able to optimise for the specific system the code is being executed on , rather than having to optimise for the general case as C + + compilers have to do .</tokentext>
<sentencetext>Read what it says again- it's not saying that Java is slow, it's just pointing out that apps wont run as fast on a phone as they do on multicore servers, because phones have much lower performance hardware.Java in terms of speed is fine, it's as fast as C++ apps in the overwhelming majority of cases, and often even faster due to being able to optimise for the specific system the code is being executed on, rather than having to optimise for the general case as C++ compilers have to do.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367314</id>
	<title>Anonymous Coward</title>
	<author>Anonymous</author>
	<datestamp>1267724400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Does the Android support flash?  If it does it will always be a better product than the iPhone!</p></htmltext>
<tokenext>Does the Android support flash ?
If it does it will always be a better product than the iPhone !</tokentext>
<sentencetext>Does the Android support flash?
If it does it will always be a better product than the iPhone!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365676</id>
	<title>Please point me to the baseband source code...</title>
	<author>Anonymous</author>
	<datestamp>1267711920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Please point me to the baseband source code...</p><p>So I can port mesh-enabled networking over to the radio chips and throw away the telephone company completely, so long as there are other people nearby with a similar device, or a public mesh access point to Internet gateway.</p><p>What's that you say?  There are Federal laws against allowing general access to programmable radios that operate in commercial frequency spectrums, and basebands have separate flash and cryptographic protection because of that?  The devil, you say!</p><p>Looks like they are about equally "open" to me...</p><p>-- AC</p></htmltext>
<tokenext>Please point me to the baseband source code...So I can port mesh-enabled networking over to the radio chips and throw away the telephone company completely , so long as there are other people nearby with a similar device , or a public mesh access point to Internet gateway.What 's that you say ?
There are Federal laws against allowing general access to programmable radios that operate in commercial frequency spectrums , and basebands have separate flash and cryptographic protection because of that ?
The devil , you say ! Looks like they are about equally " open " to me...-- AC</tokentext>
<sentencetext>Please point me to the baseband source code...So I can port mesh-enabled networking over to the radio chips and throw away the telephone company completely, so long as there are other people nearby with a similar device, or a public mesh access point to Internet gateway.What's that you say?
There are Federal laws against allowing general access to programmable radios that operate in commercial frequency spectrums, and basebands have separate flash and cryptographic protection because of that?
The devil, you say!Looks like they are about equally "open" to me...-- AC</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364190</id>
	<title>Re:No it will not</title>
	<author>SoftwareArtist</author>
	<datestamp>1267703820000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Yes they will know the syntax of the language but the libraries will be totally different.</p></div><p>Actually, they're mostly the same.  They took the standard libraries from Apache Harmony.  It's missing a few packages that aren't appropriate (like Swing), but most of what a Java programmer expects to be there, is there.
<br> <br>
Here is the index to the API docs: <a href="http://developer.android.com/reference/packages.html" title="android.com" rel="nofollow">http://developer.android.com/reference/packages.html</a> [android.com].  As you can see, a large fraction of the java.* and javax.* packages are there.</p></div>
	</htmltext>
<tokenext>Yes they will know the syntax of the language but the libraries will be totally different.Actually , they 're mostly the same .
They took the standard libraries from Apache Harmony .
It 's missing a few packages that are n't appropriate ( like Swing ) , but most of what a Java programmer expects to be there , is there .
Here is the index to the API docs : http : //developer.android.com/reference/packages.html [ android.com ] .
As you can see , a large fraction of the java .
* and javax .
* packages are there .</tokentext>
<sentencetext>Yes they will know the syntax of the language but the libraries will be totally different.Actually, they're mostly the same.
They took the standard libraries from Apache Harmony.
It's missing a few packages that aren't appropriate (like Swing), but most of what a Java programmer expects to be there, is there.
Here is the index to the API docs: http://developer.android.com/reference/packages.html [android.com].
As you can see, a large fraction of the java.
* and javax.
* packages are there.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365324</id>
	<title>Flamebait</title>
	<author>morty\_vikka</author>
	<datestamp>1267709520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Aren't a lot of developers making a lot of money as a direct result of the tight controls apple has placed on iphone apps?<br> <br>Isn't that a good thing for indy developers and small companies?<br> <br>Shouldn't devs be applauding apple's approach instead of trashing it at every opportunity?</htmltext>
<tokenext>Are n't a lot of developers making a lot of money as a direct result of the tight controls apple has placed on iphone apps ?
Is n't that a good thing for indy developers and small companies ?
Should n't devs be applauding apple 's approach instead of trashing it at every opportunity ?</tokentext>
<sentencetext>Aren't a lot of developers making a lot of money as a direct result of the tight controls apple has placed on iphone apps?
Isn't that a good thing for indy developers and small companies?
Shouldn't devs be applauding apple's approach instead of trashing it at every opportunity?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367274</id>
	<title>webOS is, perhaps, even better</title>
	<author>El Royo</author>
	<datestamp>1267724160000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Developing for webOS is perhaps even better for developers.  Personally, I hate Java.  I think I'd rather go through the pain of learning Objective C.  I wasn't a big fan of JavaScript, either, until I started working with it for webOS apps.  Now, with the PDK (plugin development kit) coming out, developers can write in C/C++ and access SDL for applications that need that extra oompf.  The underlying Linux OS is readily accessible, moreso than it is on Android, I've been given to understand.  There's a tremendous homebrew community out there creating patches, themes and more.  Check out <a href="http://webos-internals.org/" title="webos-internals.org">http://webos-internals.org/</a> [webos-internals.org] if interested in seeing that side.  And, with Palm-blessed sideloading of apps, developers can make their own way.</htmltext>
<tokenext>Developing for webOS is perhaps even better for developers .
Personally , I hate Java .
I think I 'd rather go through the pain of learning Objective C. I was n't a big fan of JavaScript , either , until I started working with it for webOS apps .
Now , with the PDK ( plugin development kit ) coming out , developers can write in C/C + + and access SDL for applications that need that extra oompf .
The underlying Linux OS is readily accessible , moreso than it is on Android , I 've been given to understand .
There 's a tremendous homebrew community out there creating patches , themes and more .
Check out http : //webos-internals.org/ [ webos-internals.org ] if interested in seeing that side .
And , with Palm-blessed sideloading of apps , developers can make their own way .</tokentext>
<sentencetext>Developing for webOS is perhaps even better for developers.
Personally, I hate Java.
I think I'd rather go through the pain of learning Objective C.  I wasn't a big fan of JavaScript, either, until I started working with it for webOS apps.
Now, with the PDK (plugin development kit) coming out, developers can write in C/C++ and access SDL for applications that need that extra oompf.
The underlying Linux OS is readily accessible, moreso than it is on Android, I've been given to understand.
There's a tremendous homebrew community out there creating patches, themes and more.
Check out http://webos-internals.org/ [webos-internals.org] if interested in seeing that side.
And, with Palm-blessed sideloading of apps, developers can make their own way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363944</id>
	<title>Re:Thanks for Playing</title>
	<author>Nerdfest</author>
	<datestamp>1267702800000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>...  on a multi-core server. Personally, I think you'd be an idiot to expect it to be either. It obviously won't run as fast, and if you haven't created the display to scale to a small screen properly, I wouldn't think it would look good either.</htmltext>
<tokenext>... on a multi-core server .
Personally , I think you 'd be an idiot to expect it to be either .
It obviously wo n't run as fast , and if you have n't created the display to scale to a small screen properly , I would n't think it would look good either .</tokentext>
<sentencetext>...  on a multi-core server.
Personally, I think you'd be an idiot to expect it to be either.
It obviously won't run as fast, and if you haven't created the display to scale to a small screen properly, I wouldn't think it would look good either.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31370894</id>
	<title>Re:3 Subjects That Make People Irrational</title>
	<author>ioliver</author>
	<datestamp>1267804320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You forgot sport!</p></htmltext>
<tokenext>You forgot sport !</tokentext>
<sentencetext>You forgot sport!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364622</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365888</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>Anonymous</author>
	<datestamp>1267713660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Which is what happens to all popular platforms.  Just look at the DS, Wii, and PS2.</p></htmltext>
<tokenext>Which is what happens to all popular platforms .
Just look at the DS , Wii , and PS2 .</tokentext>
<sentencetext>Which is what happens to all popular platforms.
Just look at the DS, Wii, and PS2.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</id>
	<title>Java as an "advantage?"</title>
	<author>Zigurd</author>
	<datestamp>1267704360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>That Java is something that makes Android superior to iPhone is a dubious claim.</p><p>Objective-C has advantages, such as that it is compiled. While Android has lots of libraries implemented in C and C++ that speed execution of Android applications, and developers can choose to implement intensive computations in C using the NDK, Objective-C requires no JNIs or other complications of splitting an implementation between Java and C/C++.</p><p>X-Code is a purpose-built, clean-sheet IDE that may lack a few power features found in Eclipse, and Eclipse has numerous plug-ins, but Eclipse also has a pretty diabolical UI, especially compared to software from Apple.</p><p>Java, Eclipse, and the other Android SDK tools are more than good enough, but they are not a big advantage, or, depending on your tastes, any advantage. There is a rough equivalence here that will probably extend to Android doing for client Java what iPhone did for Objective-C - making it popular. That is, Android apps will probably be the most common form of interactive client Java apps, if they have not already eclipsed AWT, Swing, SWT, and other Java UI libraries. This is going to have a big influence on Java, considering the fact that iPhone programming books crowd the top of the list or programming books at Amazon.</p><p>Android's advantage is in openness. Android developers are not just app developers. They can be system customizers and extenders. They can be technology vendors to a large number of OEMs using Android. They can have all kinds of products, customer, and business models, throughout the mobile economy, not just retail customers of the app store.</p></htmltext>
<tokenext>That Java is something that makes Android superior to iPhone is a dubious claim.Objective-C has advantages , such as that it is compiled .
While Android has lots of libraries implemented in C and C + + that speed execution of Android applications , and developers can choose to implement intensive computations in C using the NDK , Objective-C requires no JNIs or other complications of splitting an implementation between Java and C/C + + .X-Code is a purpose-built , clean-sheet IDE that may lack a few power features found in Eclipse , and Eclipse has numerous plug-ins , but Eclipse also has a pretty diabolical UI , especially compared to software from Apple.Java , Eclipse , and the other Android SDK tools are more than good enough , but they are not a big advantage , or , depending on your tastes , any advantage .
There is a rough equivalence here that will probably extend to Android doing for client Java what iPhone did for Objective-C - making it popular .
That is , Android apps will probably be the most common form of interactive client Java apps , if they have not already eclipsed AWT , Swing , SWT , and other Java UI libraries .
This is going to have a big influence on Java , considering the fact that iPhone programming books crowd the top of the list or programming books at Amazon.Android 's advantage is in openness .
Android developers are not just app developers .
They can be system customizers and extenders .
They can be technology vendors to a large number of OEMs using Android .
They can have all kinds of products , customer , and business models , throughout the mobile economy , not just retail customers of the app store .</tokentext>
<sentencetext>That Java is something that makes Android superior to iPhone is a dubious claim.Objective-C has advantages, such as that it is compiled.
While Android has lots of libraries implemented in C and C++ that speed execution of Android applications, and developers can choose to implement intensive computations in C using the NDK, Objective-C requires no JNIs or other complications of splitting an implementation between Java and C/C++.X-Code is a purpose-built, clean-sheet IDE that may lack a few power features found in Eclipse, and Eclipse has numerous plug-ins, but Eclipse also has a pretty diabolical UI, especially compared to software from Apple.Java, Eclipse, and the other Android SDK tools are more than good enough, but they are not a big advantage, or, depending on your tastes, any advantage.
There is a rough equivalence here that will probably extend to Android doing for client Java what iPhone did for Objective-C - making it popular.
That is, Android apps will probably be the most common form of interactive client Java apps, if they have not already eclipsed AWT, Swing, SWT, and other Java UI libraries.
This is going to have a big influence on Java, considering the fact that iPhone programming books crowd the top of the list or programming books at Amazon.Android's advantage is in openness.
Android developers are not just app developers.
They can be system customizers and extenders.
They can be technology vendors to a large number of OEMs using Android.
They can have all kinds of products, customer, and business models, throughout the mobile economy, not just retail customers of the app store.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365864</id>
	<title>Re:No it will not</title>
	<author>Anonymous</author>
	<datestamp>1267713480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It's not just AWT and Swing, many other classes are missing, e.g. ArrayDeque</p></htmltext>
<tokenext>It 's not just AWT and Swing , many other classes are missing , e.g .
ArrayDeque</tokentext>
<sentencetext>It's not just AWT and Swing, many other classes are missing, e.g.
ArrayDeque</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365376</id>
	<title>Re:It's biggest strength</title>
	<author>Anonymous</author>
	<datestamp>1267709760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Really? That's it biggest strength? And here was me thinking that technology was important. Now I find that *I* am a better phone than the iPhone! Sweet!</p></htmltext>
<tokenext>Really ?
That 's it biggest strength ?
And here was me thinking that technology was important .
Now I find that * I * am a better phone than the iPhone !
Sweet !</tokentext>
<sentencetext>Really?
That's it biggest strength?
And here was me thinking that technology was important.
Now I find that *I* am a better phone than the iPhone!
Sweet!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364746</id>
	<title>Re:That's peachy</title>
	<author>Anonymous</author>
	<datestamp>1267706100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That completely depends on your needs. This user wants to do what <i>he</i> wants with his phone, not what the manufacturer graciously allows him to do (otherwise, why get a smartphone?). Because of that, Android is an infinitely better choice than iPhone. The UI is about equal (although less pretty), and while people may bemoan the lack of apps, 95\% of the apps I've seen on the iPhone are useless. Thus, for <i>my requirements</i> (and yes, I know the mainstream user base doesn't share them. I don't care, as they are not me), Android is light-years ahead of the iPhone.</htmltext>
<tokenext>That completely depends on your needs .
This user wants to do what he wants with his phone , not what the manufacturer graciously allows him to do ( otherwise , why get a smartphone ? ) .
Because of that , Android is an infinitely better choice than iPhone .
The UI is about equal ( although less pretty ) , and while people may bemoan the lack of apps , 95 \ % of the apps I 've seen on the iPhone are useless .
Thus , for my requirements ( and yes , I know the mainstream user base does n't share them .
I do n't care , as they are not me ) , Android is light-years ahead of the iPhone .</tokentext>
<sentencetext>That completely depends on your needs.
This user wants to do what he wants with his phone, not what the manufacturer graciously allows him to do (otherwise, why get a smartphone?).
Because of that, Android is an infinitely better choice than iPhone.
The UI is about equal (although less pretty), and while people may bemoan the lack of apps, 95\% of the apps I've seen on the iPhone are useless.
Thus, for my requirements (and yes, I know the mainstream user base doesn't share them.
I don't care, as they are not me), Android is light-years ahead of the iPhone.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364106</id>
	<title>Free phone.</title>
	<author>RightSaidFred99</author>
	<datestamp>1267703520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Another great thing about Android is developers can get a <a href="http://blogs.zdnet.com/mobile-gadgeteer/?p=2601" title="zdnet.com">free phone.</a> [zdnet.com] </p></htmltext>
<tokenext>Another great thing about Android is developers can get a free phone .
[ zdnet.com ]</tokentext>
<sentencetext>Another great thing about Android is developers can get a free phone.
[zdnet.com] </sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366972</id>
	<title>Re:Java as an "advantage?"</title>
	<author>Anonymous</author>
	<datestamp>1267722000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Objective-C has advantages, such as that it is compiled.</p></div><p> <a href="http://en.wikipedia.org/wiki/Java\_compiler" title="wikipedia.org" rel="nofollow">Here's</a> [wikipedia.org] a link to a wikipedia article directing you to 3 compilers, 1 of which produces native code.</p></div>
	</htmltext>
<tokenext>Objective-C has advantages , such as that it is compiled .
Here 's [ wikipedia.org ] a link to a wikipedia article directing you to 3 compilers , 1 of which produces native code .</tokentext>
<sentencetext>Objective-C has advantages, such as that it is compiled.
Here's [wikipedia.org] a link to a wikipedia article directing you to 3 compilers, 1 of which produces native code.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364050</id>
	<title>Re:Thanks for Playing</title>
	<author>Anonymous</author>
	<datestamp>1267703220000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>As John Lennon often said, woman is the nigger of the world. Yes she is...think about it...Woman is the nigger of the world. Think about it...do something about it</p><p>We make her paint her face and dance. If she won't be a slave, we say that she don't love us. If she's real, we say she's trying to be a man. While putting her down, we pretend that she's above us</p><p>Woman is the nigger of the world...yes she is. If you don't believe me, take a look at the one you're with. Woman is the slave of the slaves. Ah, yeah...better scream about it. We make her bear and raise our children, and then we leave her flat for being a fat old mother hen. We tell her home is the only place she should be, then we complain that she's too unworldly to be our friend</p><p>We insult her every day on TV, and wonder why she has no guts or confidence. When she's young we kill her will to be free, while telling her not to be so smart we put her down for being so dumb</p><p>We make her paint her face and dance<br>We make her paint her face and dance</p></htmltext>
<tokenext>As John Lennon often said , woman is the nigger of the world .
Yes she is...think about it...Woman is the nigger of the world .
Think about it...do something about itWe make her paint her face and dance .
If she wo n't be a slave , we say that she do n't love us .
If she 's real , we say she 's trying to be a man .
While putting her down , we pretend that she 's above usWoman is the nigger of the world...yes she is .
If you do n't believe me , take a look at the one you 're with .
Woman is the slave of the slaves .
Ah , yeah...better scream about it .
We make her bear and raise our children , and then we leave her flat for being a fat old mother hen .
We tell her home is the only place she should be , then we complain that she 's too unworldly to be our friendWe insult her every day on TV , and wonder why she has no guts or confidence .
When she 's young we kill her will to be free , while telling her not to be so smart we put her down for being so dumbWe make her paint her face and danceWe make her paint her face and dance</tokentext>
<sentencetext>As John Lennon often said, woman is the nigger of the world.
Yes she is...think about it...Woman is the nigger of the world.
Think about it...do something about itWe make her paint her face and dance.
If she won't be a slave, we say that she don't love us.
If she's real, we say she's trying to be a man.
While putting her down, we pretend that she's above usWoman is the nigger of the world...yes she is.
If you don't believe me, take a look at the one you're with.
Woman is the slave of the slaves.
Ah, yeah...better scream about it.
We make her bear and raise our children, and then we leave her flat for being a fat old mother hen.
We tell her home is the only place she should be, then we complain that she's too unworldly to be our friendWe insult her every day on TV, and wonder why she has no guts or confidence.
When she's young we kill her will to be free, while telling her not to be so smart we put her down for being so dumbWe make her paint her face and danceWe make her paint her face and dance</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</id>
	<title>Shitty programmers writing shitty code.</title>
	<author>Anonymous</author>
	<datestamp>1267702380000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext><p>One of the best things about Objective-C is that it is ever so slightly more difficult than Java to learn. This has thankfully prevented it from becoming the language of choice in major outsourcing and offshoring destinations like India, Pakistan and Vietnam. It's part of the reason we don't see shitty apps on the Mac; Objective-C has historically only been used by American and European developers.</p><p>So all that Wayner is admitting is that Android will let companies continue to use these third-world developers who can't put out anything that actually works. Android phones will have a small number of useful apps, but a whole lot of utter shit developed overseas. Meanwhile, the iPhone (and soon the iPad) will be somewhat immune to this because Java isn't supported there.</p></htmltext>
<tokenext>One of the best things about Objective-C is that it is ever so slightly more difficult than Java to learn .
This has thankfully prevented it from becoming the language of choice in major outsourcing and offshoring destinations like India , Pakistan and Vietnam .
It 's part of the reason we do n't see shitty apps on the Mac ; Objective-C has historically only been used by American and European developers.So all that Wayner is admitting is that Android will let companies continue to use these third-world developers who ca n't put out anything that actually works .
Android phones will have a small number of useful apps , but a whole lot of utter shit developed overseas .
Meanwhile , the iPhone ( and soon the iPad ) will be somewhat immune to this because Java is n't supported there .</tokentext>
<sentencetext>One of the best things about Objective-C is that it is ever so slightly more difficult than Java to learn.
This has thankfully prevented it from becoming the language of choice in major outsourcing and offshoring destinations like India, Pakistan and Vietnam.
It's part of the reason we don't see shitty apps on the Mac; Objective-C has historically only been used by American and European developers.So all that Wayner is admitting is that Android will let companies continue to use these third-world developers who can't put out anything that actually works.
Android phones will have a small number of useful apps, but a whole lot of utter shit developed overseas.
Meanwhile, the iPhone (and soon the iPad) will be somewhat immune to this because Java isn't supported there.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366244</id>
	<title>Re:Java as an "advantage?"</title>
	<author>recharged95</author>
	<datestamp>1267716180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Also, Android's advantage is the JVM/DVM. Virtual machine, sandboxing, and such is cleaner to a developer to work with and can be used to keep users aware of where they are going/visiting/doing. It is the way to go for an app that really works in <i>the cloud</i>. Obj-C and the iPhone SDK are good for desktop-like mini-apps. As for networked/cloud apps, it has issues, which is another reason why the Apple appstore is locked down--they learned their lesson from Microsoft Windows: if you keep it open for developers and give full control of the hardware/filesystem, they're going to find holes and they will be exploited.
<br>
<br>

One can say each has its merits, Android more cloud network/centric and iPhone SDK more standalone/desktop-ish. Hence why games clearly work better on the iPhone (desktop-console games &gt; network games currently). I tried WebOS and it's very promising more JS/Flash centric style, but it has a way to go as well. The Android team should look into JavaFx along with Flash for their OS enhancements...
<br>
<br>

I found a lot of graphics power and h/w usability with the iPhone SDK over the Android SDK, but I and other iphone app-devs rely on Apple's closed nature for security with webapps. I talk to devs and most don't even think about security--the SDK pretty much obscures that concept. Otherwise, it's easy to write an app that takes CC data, personal data, usage tracking, etc.. without knowing it's accessible. Also, when the iPhone crashes, it crashes <b>hard</b> whereas I can still hold a phone call on Android hardware if an app crashes (or force close it).... Of course, Apple is addressing security thru deployment via XCode settings (and the millions of menus/plists) instead of the VM and XML files (Android).
<br>

<br>
And lastly, ok, fanboy comment, but Eclipse tabs &gt; XCode windows for editing. <i> Really.</i></htmltext>
<tokenext>Also , Android 's advantage is the JVM/DVM .
Virtual machine , sandboxing , and such is cleaner to a developer to work with and can be used to keep users aware of where they are going/visiting/doing .
It is the way to go for an app that really works in the cloud .
Obj-C and the iPhone SDK are good for desktop-like mini-apps .
As for networked/cloud apps , it has issues , which is another reason why the Apple appstore is locked down--they learned their lesson from Microsoft Windows : if you keep it open for developers and give full control of the hardware/filesystem , they 're going to find holes and they will be exploited .
One can say each has its merits , Android more cloud network/centric and iPhone SDK more standalone/desktop-ish .
Hence why games clearly work better on the iPhone ( desktop-console games &gt; network games currently ) .
I tried WebOS and it 's very promising more JS/Flash centric style , but it has a way to go as well .
The Android team should look into JavaFx along with Flash for their OS enhancements.. . I found a lot of graphics power and h/w usability with the iPhone SDK over the Android SDK , but I and other iphone app-devs rely on Apple 's closed nature for security with webapps .
I talk to devs and most do n't even think about security--the SDK pretty much obscures that concept .
Otherwise , it 's easy to write an app that takes CC data , personal data , usage tracking , etc.. without knowing it 's accessible .
Also , when the iPhone crashes , it crashes hard whereas I can still hold a phone call on Android hardware if an app crashes ( or force close it ) .... Of course , Apple is addressing security thru deployment via XCode settings ( and the millions of menus/plists ) instead of the VM and XML files ( Android ) .
And lastly , ok , fanboy comment , but Eclipse tabs &gt; XCode windows for editing .
Really .</tokentext>
<sentencetext>Also, Android's advantage is the JVM/DVM.
Virtual machine, sandboxing, and such is cleaner to a developer to work with and can be used to keep users aware of where they are going/visiting/doing.
It is the way to go for an app that really works in the cloud.
Obj-C and the iPhone SDK are good for desktop-like mini-apps.
As for networked/cloud apps, it has issues, which is another reason why the Apple appstore is locked down--they learned their lesson from Microsoft Windows: if you keep it open for developers and give full control of the hardware/filesystem, they're going to find holes and they will be exploited.
One can say each has its merits, Android more cloud network/centric and iPhone SDK more standalone/desktop-ish.
Hence why games clearly work better on the iPhone (desktop-console games &gt; network games currently).
I tried WebOS and it's very promising more JS/Flash centric style, but it has a way to go as well.
The Android team should look into JavaFx along with Flash for their OS enhancements...



I found a lot of graphics power and h/w usability with the iPhone SDK over the Android SDK, but I and other iphone app-devs rely on Apple's closed nature for security with webapps.
I talk to devs and most don't even think about security--the SDK pretty much obscures that concept.
Otherwise, it's easy to write an app that takes CC data, personal data, usage tracking, etc.. without knowing it's accessible.
Also, when the iPhone crashes, it crashes hard whereas I can still hold a phone call on Android hardware if an app crashes (or force close it).... Of course, Apple is addressing security thru deployment via XCode settings (and the millions of menus/plists) instead of the VM and XML files (Android).
And lastly, ok, fanboy comment, but Eclipse tabs &gt; XCode windows for editing.
Really.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364826</id>
	<title>author's programming chops</title>
	<author>Sebastopol</author>
	<datestamp>1267706520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>But if I turned it back to portrait, it mysteriously worked because the bounding rectangle for the screen was now taller, not wider. That took more than a few minutes to find.</i></p><p>He's an app developer for mobile, but doesn't have the forethought to code for variable display sizes?  rtard.</p></htmltext>
<tokenext>But if I turned it back to portrait , it mysteriously worked because the bounding rectangle for the screen was now taller , not wider .
That took more than a few minutes to find.He 's an app developer for mobile , but does n't have the forethought to code for variable display sizes ?
rtard .</tokentext>
<sentencetext>But if I turned it back to portrait, it mysteriously worked because the bounding rectangle for the screen was now taller, not wider.
That took more than a few minutes to find.He's an app developer for mobile, but doesn't have the forethought to code for variable display sizes?
rtard.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>modmans2ndcoming</author>
	<datestamp>1267702920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>As far as I can tell, 99\% of the iphone apps are pure and utter shit.</p></htmltext>
<tokenext>As far as I can tell , 99 \ % of the iphone apps are pure and utter shit .</tokentext>
<sentencetext>As far as I can tell, 99\% of the iphone apps are pure and utter shit.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364784</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>Anonymous</author>
	<datestamp>1267706280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You clearly misunderstand. There are at least two distinct type of "shitty software".</p><p>1) Software that's useless. This is the sort of software you're referring to. They are apps that look like they might be useful, but in the end they just aren't.</p><p>2) Software that's horrible designed and implemented. That's what the GP was talking about. India is the main producer of these shitty apps, written by people who don't have even the slightest clue about developing software.</p></htmltext>
<tokenext>You clearly misunderstand .
There are at least two distinct type of " shitty software " .1 ) Software that 's useless .
This is the sort of software you 're referring to .
They are apps that look like they might be useful , but in the end they just are n't.2 ) Software that 's horrible designed and implemented .
That 's what the GP was talking about .
India is the main producer of these shitty apps , written by people who do n't have even the slightest clue about developing software .</tokentext>
<sentencetext>You clearly misunderstand.
There are at least two distinct type of "shitty software".1) Software that's useless.
This is the sort of software you're referring to.
They are apps that look like they might be useful, but in the end they just aren't.2) Software that's horrible designed and implemented.
That's what the GP was talking about.
India is the main producer of these shitty apps, written by people who don't have even the slightest clue about developing software.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367200</id>
	<title>Re:Use "em" not "px" when defining the UI</title>
	<author>Skreems</author>
	<datestamp>1267723740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Android does have dynamic DPI-based resizing built in for all graphics assets. It will also let you define "flex" images where sections of the side and center are repeated to stretch the image to different sized content without rescaling. Between the two, it's pretty easy to not care about pixel sizes.</htmltext>
<tokenext>Android does have dynamic DPI-based resizing built in for all graphics assets .
It will also let you define " flex " images where sections of the side and center are repeated to stretch the image to different sized content without rescaling .
Between the two , it 's pretty easy to not care about pixel sizes .</tokentext>
<sentencetext>Android does have dynamic DPI-based resizing built in for all graphics assets.
It will also let you define "flex" images where sections of the side and center are repeated to stretch the image to different sized content without rescaling.
Between the two, it's pretty easy to not care about pixel sizes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365720</id>
	<title>Re:meh</title>
	<author>Anonymous</author>
	<datestamp>1267712220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Can I run JavaFX?</p></htmltext>
<tokenext>Can I run JavaFX ?</tokentext>
<sentencetext>Can I run JavaFX?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31406962</id>
	<title>Re:wake me up when it catches up</title>
	<author>jamshid</author>
	<datestamp>1268048760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Couple of things to keep in mind in the iPhone vs Android development wars:</p><p>1) Android also allows native (C/C++) development with the Android Native Development Kit (NDK): <a href="http://developer.android.com/sdk/ndk/index.html#overview" title="android.com" rel="nofollow">http://developer.android.com/sdk/ndk/index.html#overview</a> [android.com]</p><p>2) If Android apps do become popular and a competitive advantage, AFAIK there's nothing to stop Apple or someone else from porting Dalvik and underlying libraries and services to the iPhone. After all, both the iPhone and Android are at their cores just little unix boxes. If so, the project should be called Blade Runner. The Warner Bros lawsuit would be good publicity.</p></htmltext>
<tokenext>Couple of things to keep in mind in the iPhone vs Android development wars : 1 ) Android also allows native ( C/C + + ) development with the Android Native Development Kit ( NDK ) : http : //developer.android.com/sdk/ndk/index.html # overview [ android.com ] 2 ) If Android apps do become popular and a competitive advantage , AFAIK there 's nothing to stop Apple or someone else from porting Dalvik and underlying libraries and services to the iPhone .
After all , both the iPhone and Android are at their cores just little unix boxes .
If so , the project should be called Blade Runner .
The Warner Bros lawsuit would be good publicity .</tokentext>
<sentencetext>Couple of things to keep in mind in the iPhone vs Android development wars:1) Android also allows native (C/C++) development with the Android Native Development Kit (NDK): http://developer.android.com/sdk/ndk/index.html#overview [android.com]2) If Android apps do become popular and a competitive advantage, AFAIK there's nothing to stop Apple or someone else from porting Dalvik and underlying libraries and services to the iPhone.
After all, both the iPhone and Android are at their cores just little unix boxes.
If so, the project should be called Blade Runner.
The Warner Bros lawsuit would be good publicity.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366356</id>
	<title>It is not the developers' perspective that matters</title>
	<author>QuietLagoon</author>
	<datestamp>1267717320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It is the customers' perspective that matters.   Far too often developers think the world revolves around themselves.  It doesn't.</htmltext>
<tokenext>It is the customers ' perspective that matters .
Far too often developers think the world revolves around themselves .
It does n't .</tokentext>
<sentencetext>It is the customers' perspective that matters.
Far too often developers think the world revolves around themselves.
It doesn't.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364176</id>
	<title>Re:meh</title>
	<author>h4rr4r</author>
	<datestamp>1267703820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The n900 still uses binary drivers, which means when the n901 ships good luck with that.</p></htmltext>
<tokenext>The n900 still uses binary drivers , which means when the n901 ships good luck with that .</tokentext>
<sentencetext>The n900 still uses binary drivers, which means when the n901 ships good luck with that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369848</id>
	<title>Troll?</title>
	<author>Jesus\_666</author>
	<datestamp>1267797480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Of course I didn't read much of TFA. Then again, an article with comments like "While iPhone developers have found that one path to success is playing to our baser instincts (until Apple shuts them down), a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket" can't be very objective. Yeah, you don't like the iPhone. We get it. Now can we please get a developer who isn't obviously biased to compare the two platforms? Or at least one who can hide his bias for more than three paragraphs?</htmltext>
<tokenext>Of course I did n't read much of TFA .
Then again , an article with comments like " While iPhone developers have found that one path to success is playing to our baser instincts ( until Apple shuts them down ) , a number of Android applications are offering practical solutions that unlock the power of a phone that 's really a Unix machine you can slip into your pocket " ca n't be very objective .
Yeah , you do n't like the iPhone .
We get it .
Now can we please get a developer who is n't obviously biased to compare the two platforms ?
Or at least one who can hide his bias for more than three paragraphs ?</tokentext>
<sentencetext>Of course I didn't read much of TFA.
Then again, an article with comments like "While iPhone developers have found that one path to success is playing to our baser instincts (until Apple shuts them down), a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket" can't be very objective.
Yeah, you don't like the iPhone.
We get it.
Now can we please get a developer who isn't obviously biased to compare the two platforms?
Or at least one who can hide his bias for more than three paragraphs?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758</id>
	<title>It's biggest strength</title>
	<author>Anonymous</author>
	<datestamp>1267701960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>It's not DRM-laden patent trolling Apple.</p></htmltext>
<tokenext>It 's not DRM-laden patent trolling Apple .</tokentext>
<sentencetext>It's not DRM-laden patent trolling Apple.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363880</id>
	<title>Oh boy!</title>
	<author>Anonymous</author>
	<datestamp>1267702500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>...it won't look pretty or run as fast as it does on multicore servers.</p></div></blockquote><p>Beats the iPhone in slow-running, ugly applications.  Take that Apple!</p></div>
	</htmltext>
<tokenext>...it wo n't look pretty or run as fast as it does on multicore servers.Beats the iPhone in slow-running , ugly applications .
Take that Apple !</tokentext>
<sentencetext>...it won't look pretty or run as fast as it does on multicore servers.Beats the iPhone in slow-running, ugly applications.
Take that Apple!
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367582</id>
	<title>Re:When will we learn...</title>
	<author>pydev</author>
	<datestamp>1267726680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>but if smartphones are going to take over the world I would not want my grandmother to have to deal with fragmentation and software complexity.</i></p><p>You're suggesting that the iPhone is less complex?  Don't make me laugh.</p></htmltext>
<tokenext>but if smartphones are going to take over the world I would not want my grandmother to have to deal with fragmentation and software complexity.You 're suggesting that the iPhone is less complex ?
Do n't make me laugh .</tokentext>
<sentencetext>but if smartphones are going to take over the world I would not want my grandmother to have to deal with fragmentation and software complexity.You're suggesting that the iPhone is less complex?
Don't make me laugh.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365572</id>
	<title>And geeks are such great predictors of success...</title>
	<author>sootman</author>
	<datestamp>1267711080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"... a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket... Any Java developer familiar with Eclipse should be able to use Google's Android documentation to turn out a very basic application in just a few hours."</p><p>It also has wireless, and more space than a Nomad. The iPhone's defeat is imminent!</p></htmltext>
<tokenext>" ... a number of Android applications are offering practical solutions that unlock the power of a phone that 's really a Unix machine you can slip into your pocket... Any Java developer familiar with Eclipse should be able to use Google 's Android documentation to turn out a very basic application in just a few hours .
" It also has wireless , and more space than a Nomad .
The iPhone 's defeat is imminent !</tokentext>
<sentencetext>"... a number of Android applications are offering practical solutions that unlock the power of a phone that's really a Unix machine you can slip into your pocket... Any Java developer familiar with Eclipse should be able to use Google's Android documentation to turn out a very basic application in just a few hours.
"It also has wireless, and more space than a Nomad.
The iPhone's defeat is imminent!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31370546</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>mcvos</author>
	<datestamp>1267802340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Unfortunately, Java is a backwards language with zero interesting features whatsoever.</p></div><p>Other than the JVM, that is. Java sucks, but the JVM is the coolest thing ever, and it supports Scala, Groovy, JRuby, Jython, etc.</p><p>Java was great when all we knew was C++, but nowadays we have much better choices available. And we get to keep the one good thing that Java ever gave us.</p></div>
	</htmltext>
<tokenext>Unfortunately , Java is a backwards language with zero interesting features whatsoever.Other than the JVM , that is .
Java sucks , but the JVM is the coolest thing ever , and it supports Scala , Groovy , JRuby , Jython , etc.Java was great when all we knew was C + + , but nowadays we have much better choices available .
And we get to keep the one good thing that Java ever gave us .</tokentext>
<sentencetext>Unfortunately, Java is a backwards language with zero interesting features whatsoever.Other than the JVM, that is.
Java sucks, but the JVM is the coolest thing ever, and it supports Scala, Groovy, JRuby, Jython, etc.Java was great when all we knew was C++, but nowadays we have much better choices available.
And we get to keep the one good thing that Java ever gave us.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365838</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364722</id>
	<title>Re:Thanks for Playing</title>
	<author>bmecoli</author>
	<datestamp>1267706040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>"although it won't look pretty or run as fast..."</p></div><p>"...as it does on multicore servers."  Way to quote out of context there.  Who modded this insightful, really?</p></div>
	</htmltext>
<tokenext>" although it wo n't look pretty or run as fast... " " ...as it does on multicore servers .
" Way to quote out of context there .
Who modded this insightful , really ?</tokentext>
<sentencetext>"although it won't look pretty or run as fast...""...as it does on multicore servers.
"  Way to quote out of context there.
Who modded this insightful, really?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365594</id>
	<title>Re:It's biggest strength</title>
	<author>Anonymous</author>
	<datestamp>1267711200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>... is getting to put a good programming environment on it in place of that with which it comes.</p></htmltext>
<tokenext>... is getting to put a good programming environment on it in place of that with which it comes .</tokentext>
<sentencetext>... is getting to put a good programming environment on it in place of that with which it comes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364690</id>
	<title>Syntax</title>
	<author>mosb1000</author>
	<datestamp>1267705920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No kidding, who cares about syntax?  That's maybe 1\% of programming, the rest is creativity and knowing the libraries.  If the libraries don't transfer, you have kept almost nothing.</htmltext>
<tokenext>No kidding , who cares about syntax ?
That 's maybe 1 \ % of programming , the rest is creativity and knowing the libraries .
If the libraries do n't transfer , you have kept almost nothing .</tokentext>
<sentencetext>No kidding, who cares about syntax?
That's maybe 1\% of programming, the rest is creativity and knowing the libraries.
If the libraries don't transfer, you have kept almost nothing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365308</id>
	<title>Use Intellij IDEA</title>
	<author>SoftwareArtist</author>
	<datestamp>1267709400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Agreed about the Eclipse UI.  If you're going to do Android development, use Intellij IDEA, which has quite good Android support and is a vastly superior IDE.</htmltext>
<tokenext>Agreed about the Eclipse UI .
If you 're going to do Android development , use Intellij IDEA , which has quite good Android support and is a vastly superior IDE .</tokentext>
<sentencetext>Agreed about the Eclipse UI.
If you're going to do Android development, use Intellij IDEA, which has quite good Android support and is a vastly superior IDE.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31371124</id>
	<title>Re:Developers Developers Developers</title>
	<author>Anonymous</author>
	<datestamp>1267805280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It might well be (it can be both, ya' know) but why exactly would we be discussing the user experience in the <a href="http://slashdot.org/tag/developers" title="slashdot.org" rel="nofollow">Developers section</a> [slashdot.org] of Slashdot?</p></htmltext>
<tokenext>It might well be ( it can be both , ya ' know ) but why exactly would we be discussing the user experience in the Developers section [ slashdot.org ] of Slashdot ?</tokentext>
<sentencetext>It might well be (it can be both, ya' know) but why exactly would we be discussing the user experience in the Developers section [slashdot.org] of Slashdot?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363772</id>
	<title>haahahaahahaahahaahahaahaaaaaa!</title>
	<author>Anonymous</author>
	<datestamp>1267702080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><i>No.</i></p></htmltext>
<tokenext>No .</tokentext>
<sentencetext>No.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369240</id>
	<title>Re:Developers Developers Developers</title>
	<author>Anonymous</author>
	<datestamp>1267790160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yea I just hate reading an article that applies to devs on Slashdot.</p></htmltext>
<tokenext>Yea I just hate reading an article that applies to devs on Slashdot .</tokentext>
<sentencetext>Yea I just hate reading an article that applies to devs on Slashdot.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368256</id>
	<title>Re: Meh</title>
	<author>Ecuador</author>
	<datestamp>1267820820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>I am a proud owner of a N900 for a week now. It is the first time a phone truly amazes me, and that is of course all thanks to the OS.  I am a mobile developer, so I have so far developed for and owned BREW, Symbian and iPhone OS devices. I liked developing for the iphone, hated the other two, but from a user standpoint I did not enjoy any device, since even browsing was painful (no, I don't consider the iphone's ultra low res usable), and they wouldn't let me do much more than that.<br>Enter the N900. Android is not a unix machine in your pocket, it is a jvm running java apps on top of a unix kernel, when Maemo is a full debian based distro. Things like opening several browser windows, running apt-get install in the background and switching (kind of expose-style) between them is easy on the device. With an 800x480 res and a full browser (Mozilla based with flash and everything) it is the first time I can browse from a phone (as I am doing right now). As a developer I really appreciated that I could do "apt-get install subversion", sync with my svn server and edit my code with vim.<br>Don,t get me wrong, I also like android and usually recommend something like a nexus one to nom-power users, but I am sure the average slashdotter would really get excited with Maemo, not android.</p></htmltext>
<tokenext>I am a proud owner of a N900 for a week now .
It is the first time a phone truly amazes me , and that is of course all thanks to the OS .
I am a mobile developer , so I have so far developed for and owned BREW , Symbian and iPhone OS devices .
I liked developing for the iphone , hated the other two , but from a user standpoint I did not enjoy any device , since even browsing was painful ( no , I do n't consider the iphone 's ultra low res usable ) , and they would n't let me do much more than that.Enter the N900 .
Android is not a unix machine in your pocket , it is a jvm running java apps on top of a unix kernel , when Maemo is a full debian based distro .
Things like opening several browser windows , running apt-get install in the background and switching ( kind of expose-style ) between them is easy on the device .
With an 800x480 res and a full browser ( Mozilla based with flash and everything ) it is the first time I can browse from a phone ( as I am doing right now ) .
As a developer I really appreciated that I could do " apt-get install subversion " , sync with my svn server and edit my code with vim.Don,t get me wrong , I also like android and usually recommend something like a nexus one to nom-power users , but I am sure the average slashdotter would really get excited with Maemo , not android .</tokentext>
<sentencetext>I am a proud owner of a N900 for a week now.
It is the first time a phone truly amazes me, and that is of course all thanks to the OS.
I am a mobile developer, so I have so far developed for and owned BREW, Symbian and iPhone OS devices.
I liked developing for the iphone, hated the other two, but from a user standpoint I did not enjoy any device, since even browsing was painful (no, I don't consider the iphone's ultra low res usable), and they wouldn't let me do much more than that.Enter the N900.
Android is not a unix machine in your pocket, it is a jvm running java apps on top of a unix kernel, when Maemo is a full debian based distro.
Things like opening several browser windows, running apt-get install in the background and switching (kind of expose-style) between them is easy on the device.
With an 800x480 res and a full browser (Mozilla based with flash and everything) it is the first time I can browse from a phone (as I am doing right now).
As a developer I really appreciated that I could do "apt-get install subversion", sync with my svn server and edit my code with vim.Don,t get me wrong, I also like android and usually recommend something like a nexus one to nom-power users, but I am sure the average slashdotter would really get excited with Maemo, not android.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365566</id>
	<title>Re:meh</title>
	<author>Anonymous</author>
	<datestamp>1267711020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Moblin is just as dead as Maemo. They're both becoming <a href="http://meego.com/" title="meego.com" rel="nofollow">MeeGo</a> [meego.com]. Moblin and Maemo were very similar anyway. The first release of MeeGo will target Intel Atom systems and the Nokia N900:</p><p><a href="http://meego.com/community/blogs/valhalla/2010/towards-day-one" title="meego.com" rel="nofollow">http://meego.com/community/blogs/valhalla/2010/towards-day-one</a> [meego.com]</p></htmltext>
<tokenext>Moblin is just as dead as Maemo .
They 're both becoming MeeGo [ meego.com ] .
Moblin and Maemo were very similar anyway .
The first release of MeeGo will target Intel Atom systems and the Nokia N900 : http : //meego.com/community/blogs/valhalla/2010/towards-day-one [ meego.com ]</tokentext>
<sentencetext>Moblin is just as dead as Maemo.
They're both becoming MeeGo [meego.com].
Moblin and Maemo were very similar anyway.
The first release of MeeGo will target Intel Atom systems and the Nokia N900:http://meego.com/community/blogs/valhalla/2010/towards-day-one [meego.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365200</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365182</id>
	<title>Re:wake me up when it catches up</title>
	<author>rxan</author>
	<datestamp>1267708500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>You can buy and play FIFA10 or even Grand Theft Auto on the iPhone. The games are a pretty good indicator IMHO. When complex and expensive productions from big studios start coming out for a platform, you know that the platform is popular.</p></div><p>You're talking about porting applications though. That's different from developing apps "from scratch" for a platform.</p><p>The reason there are so many games on the iPhone isn't because it's "easier" to develop for. I'm not saying it is easier. It's because it supports C++ and the major dev houses can easily throw their code on it and run it. Yes there are some modifications, but not much is required. Most games aren't written in Java for the obvious performance reasons.</p></div>
	</htmltext>
<tokenext>You can buy and play FIFA10 or even Grand Theft Auto on the iPhone .
The games are a pretty good indicator IMHO .
When complex and expensive productions from big studios start coming out for a platform , you know that the platform is popular.You 're talking about porting applications though .
That 's different from developing apps " from scratch " for a platform.The reason there are so many games on the iPhone is n't because it 's " easier " to develop for .
I 'm not saying it is easier .
It 's because it supports C + + and the major dev houses can easily throw their code on it and run it .
Yes there are some modifications , but not much is required .
Most games are n't written in Java for the obvious performance reasons .</tokentext>
<sentencetext>You can buy and play FIFA10 or even Grand Theft Auto on the iPhone.
The games are a pretty good indicator IMHO.
When complex and expensive productions from big studios start coming out for a platform, you know that the platform is popular.You're talking about porting applications though.
That's different from developing apps "from scratch" for a platform.The reason there are so many games on the iPhone isn't because it's "easier" to develop for.
I'm not saying it is easier.
It's because it supports C++ and the major dev houses can easily throw their code on it and run it.
Yes there are some modifications, but not much is required.
Most games aren't written in Java for the obvious performance reasons.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365340</id>
	<title>It's like comparing bad to worse.</title>
	<author>zullnero</author>
	<datestamp>1267709580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Seriously, neither Android nor iPhone are all that great for serious development.  They're both underwhelming platforms for real mobile development.  Android has a leg up in many aspects as it embraces more open methods of development and more open standards, but when the dust clears, both platforms have been pushed to the forefront as a result of marketing hype.
<br> <br>
There are better options out there, but most of us mobile developers who know there are better options have been herded along with the flock of sheep simply because we have to develop apps that the biggest flock of sheep will use or end up wasting our time and effort.  Compared to more comprehensive and seriously powerful applications we used to write for older mobile OS's, the bulk of them these days are basically crapware.</htmltext>
<tokenext>Seriously , neither Android nor iPhone are all that great for serious development .
They 're both underwhelming platforms for real mobile development .
Android has a leg up in many aspects as it embraces more open methods of development and more open standards , but when the dust clears , both platforms have been pushed to the forefront as a result of marketing hype .
There are better options out there , but most of us mobile developers who know there are better options have been herded along with the flock of sheep simply because we have to develop apps that the biggest flock of sheep will use or end up wasting our time and effort .
Compared to more comprehensive and seriously powerful applications we used to write for older mobile OS 's , the bulk of them these days are basically crapware .</tokentext>
<sentencetext>Seriously, neither Android nor iPhone are all that great for serious development.
They're both underwhelming platforms for real mobile development.
Android has a leg up in many aspects as it embraces more open methods of development and more open standards, but when the dust clears, both platforms have been pushed to the forefront as a result of marketing hype.
There are better options out there, but most of us mobile developers who know there are better options have been herded along with the flock of sheep simply because we have to develop apps that the biggest flock of sheep will use or end up wasting our time and effort.
Compared to more comprehensive and seriously powerful applications we used to write for older mobile OS's, the bulk of them these days are basically crapware.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365316</id>
	<title>Re:Use "em" not "px" when defining the UI</title>
	<author>mdwh2</author>
	<datestamp>1267709460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Who says bitmaps need to resize? A rescaling GUI doesn't mean that everything has to scale uniformly, it just means using the extra space sensibly. Try resizing your browser window right now - does everything scale exactly the same? Of course not. Is it useful to be able to enlarge the window? Of course.</p><p>Bitmaps are generally a minor part of GUIs anyway. And if you're talking about games instead, that's the first place you should be learning to program resizeable displays.</p></htmltext>
<tokenext>Who says bitmaps need to resize ?
A rescaling GUI does n't mean that everything has to scale uniformly , it just means using the extra space sensibly .
Try resizing your browser window right now - does everything scale exactly the same ?
Of course not .
Is it useful to be able to enlarge the window ?
Of course.Bitmaps are generally a minor part of GUIs anyway .
And if you 're talking about games instead , that 's the first place you should be learning to program resizeable displays .</tokentext>
<sentencetext>Who says bitmaps need to resize?
A rescaling GUI doesn't mean that everything has to scale uniformly, it just means using the extra space sensibly.
Try resizing your browser window right now - does everything scale exactly the same?
Of course not.
Is it useful to be able to enlarge the window?
Of course.Bitmaps are generally a minor part of GUIs anyway.
And if you're talking about games instead, that's the first place you should be learning to program resizeable displays.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364612</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>greencpu</author>
	<datestamp>1267705560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>hard to believe a guy with this elitist attitude uses a mac.</htmltext>
<tokenext>hard to believe a guy with this elitist attitude uses a mac .</tokentext>
<sentencetext>hard to believe a guy with this elitist attitude uses a mac.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365480</id>
	<title>Re:wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267710480000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Internet access. Mapping software. Communication. Taking/showing photos and video. Playing music. Running useful utilities (there's more to life than spreadsheets). And *gasp* phone calls.</p><p>If all you want to use it for is playing hand held video games, then there are better - and more popular, incidentally - devices for that.</p><p>And come on - every time someone points out one of the <i>many</i> basic features that the Iphone lacks or lacked, we get no end of "Why would I want to do that?" So here we are, saying "Why would we want to run video games on a phone?" You only cling to this as being an important, because it's something that the Iphone can do. Next, you'll be telling me how fundamentally important you think multitouch is.</p></htmltext>
<tokenext>Internet access .
Mapping software .
Communication. Taking/showing photos and video .
Playing music .
Running useful utilities ( there 's more to life than spreadsheets ) .
And * gasp * phone calls.If all you want to use it for is playing hand held video games , then there are better - and more popular , incidentally - devices for that.And come on - every time someone points out one of the many basic features that the Iphone lacks or lacked , we get no end of " Why would I want to do that ?
" So here we are , saying " Why would we want to run video games on a phone ?
" You only cling to this as being an important , because it 's something that the Iphone can do .
Next , you 'll be telling me how fundamentally important you think multitouch is .</tokentext>
<sentencetext>Internet access.
Mapping software.
Communication. Taking/showing photos and video.
Playing music.
Running useful utilities (there's more to life than spreadsheets).
And *gasp* phone calls.If all you want to use it for is playing hand held video games, then there are better - and more popular, incidentally - devices for that.And come on - every time someone points out one of the many basic features that the Iphone lacks or lacked, we get no end of "Why would I want to do that?
" So here we are, saying "Why would we want to run video games on a phone?
" You only cling to this as being an important, because it's something that the Iphone can do.
Next, you'll be telling me how fundamentally important you think multitouch is.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364900</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918</id>
	<title>Developers Developers Developers</title>
	<author>Anonymous</author>
	<datestamp>1267702680000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>Android not only competitive but in fact a better choice than the iPhone for many developers, largely due to its Java foundation.</i></p><p>Now I don't want an Android phone. I thought it would be good or better for me as a USER, not as a developer. Silly me.</p></htmltext>
<tokenext>Android not only competitive but in fact a better choice than the iPhone for many developers , largely due to its Java foundation.Now I do n't want an Android phone .
I thought it would be good or better for me as a USER , not as a developer .
Silly me .</tokentext>
<sentencetext>Android not only competitive but in fact a better choice than the iPhone for many developers, largely due to its Java foundation.Now I don't want an Android phone.
I thought it would be good or better for me as a USER, not as a developer.
Silly me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</id>
	<title>No it will not</title>
	<author>LWATCDR</author>
	<datestamp>1267702440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>"Not only that, but all of the code from other Java programs will run on your Android phone &mdash; although it won't look pretty or run as fast as it does on multicore servers.'""<br>No because if it has any type of UI odds are that uses swing or awt. Not only that but I doubt that the Android JVM has all the standard libraries that are available on Sun Java.<br>Yes they will know the syntax of the language but the libraries will be totally different.<br>Not to mention that is probably very little code running on servers that you will want to run on a phone.</p><p>And yes I write in java and I have an Android phone and I have looked at the Android SDK.</p></htmltext>
<tokenext>" Not only that , but all of the code from other Java programs will run on your Android phone    although it wo n't look pretty or run as fast as it does on multicore servers .
' " " No because if it has any type of UI odds are that uses swing or awt .
Not only that but I doubt that the Android JVM has all the standard libraries that are available on Sun Java.Yes they will know the syntax of the language but the libraries will be totally different.Not to mention that is probably very little code running on servers that you will want to run on a phone.And yes I write in java and I have an Android phone and I have looked at the Android SDK .</tokentext>
<sentencetext>"Not only that, but all of the code from other Java programs will run on your Android phone — although it won't look pretty or run as fast as it does on multicore servers.
'""No because if it has any type of UI odds are that uses swing or awt.
Not only that but I doubt that the Android JVM has all the standard libraries that are available on Sun Java.Yes they will know the syntax of the language but the libraries will be totally different.Not to mention that is probably very little code running on servers that you will want to run on a phone.And yes I write in java and I have an Android phone and I have looked at the Android SDK.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365570</id>
	<title>From Brainwashed Follower of Steve Jobs</title>
	<author>Anonymous</author>
	<datestamp>1267711020000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>SCREW android!! SCREW java!! SCREW YOU!!!</p><p>no, I mean REALLY. This isn't a joke.</p></htmltext>
<tokenext>SCREW android ! !
SCREW java ! !
SCREW YOU ! !
! no , I mean REALLY .
This is n't a joke .</tokentext>
<sentencetext>SCREW android!!
SCREW java!!
SCREW YOU!!
!no, I mean REALLY.
This isn't a joke.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31374664</id>
	<title>Re:Java as an "advantage?"</title>
	<author>JAlexoi</author>
	<datestamp>1267822080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hm.. How about NOT NEEDING TO LEARN A NEW LANGUAGE for an advantage? You know that Java is probably the most wide-spread programming language ATM, do you? That is the whole point. Not how people feel about Java, not drawbacks of a VM based system and so on...</htmltext>
<tokenext>Hm.. How about NOT NEEDING TO LEARN A NEW LANGUAGE for an advantage ?
You know that Java is probably the most wide-spread programming language ATM , do you ?
That is the whole point .
Not how people feel about Java , not drawbacks of a VM based system and so on.. .</tokentext>
<sentencetext>Hm.. How about NOT NEEDING TO LEARN A NEW LANGUAGE for an advantage?
You know that Java is probably the most wide-spread programming language ATM, do you?
That is the whole point.
Not how people feel about Java, not drawbacks of a VM based system and so on...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940</id>
	<title>Windows Mobile</title>
	<author>Dan East</author>
	<datestamp>1267702800000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Then according to his logic, Windows Mobile is better than Android and iPhone combined, because not only can it run Java apps, but you can author software for it in practically any mainstream programming language.</p><p>What about Blackberry? It is a pure Java based platform, even more so than Android.</p><p>I just think it's silly to say "This device is LISP based, so it is better than device X because some corporation might have LISP developers sitting around that can write apps for it in a language they're used to!"</p></htmltext>
<tokenext>Then according to his logic , Windows Mobile is better than Android and iPhone combined , because not only can it run Java apps , but you can author software for it in practically any mainstream programming language.What about Blackberry ?
It is a pure Java based platform , even more so than Android.I just think it 's silly to say " This device is LISP based , so it is better than device X because some corporation might have LISP developers sitting around that can write apps for it in a language they 're used to !
"</tokentext>
<sentencetext>Then according to his logic, Windows Mobile is better than Android and iPhone combined, because not only can it run Java apps, but you can author software for it in practically any mainstream programming language.What about Blackberry?
It is a pure Java based platform, even more so than Android.I just think it's silly to say "This device is LISP based, so it is better than device X because some corporation might have LISP developers sitting around that can write apps for it in a language they're used to!
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364290</id>
	<title>Re:Thanks for Playing</title>
	<author>Anonymous</author>
	<datestamp>1267704300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yeah, I thought that was funny, but the other big thing is that they're missing the point.</p><p>Yes, Java developers can adapt quickly to a new Java API, surprise!</p><p>The iPhone runs a version of Cocoa and you write that in ObjC, just like...every other Apple system!  So guess what?  Objective-C developers can adapt quickly to a new Objective-C API!</p><p>The point is that yeah, iPhone may not get as many "general" developers as the Android, but is that really Apple's goal? Apple is doing the same thing they did with the iPod - cross-selling!  Part of why I find the iPhone useful personally is because the apps have a similar ideology to the apps I use on my Macbook Pro.  A lot of popular apps for Mac have syncing versions that are ran on the iPhone.  This applies to some cross platform stuff too, a lot of it starts on Mac, then eventually they port it to PC after they have an iPhone app.</p><p>So no, Apple doesn't benefit from a huge Java community, they benefit from the extremely \_LOYAL\_ objective-c community, which since OpenStep is not too popular, is pretty much entirely Apple-centric.</p></htmltext>
<tokenext>Yeah , I thought that was funny , but the other big thing is that they 're missing the point.Yes , Java developers can adapt quickly to a new Java API , surprise ! The iPhone runs a version of Cocoa and you write that in ObjC , just like...every other Apple system !
So guess what ?
Objective-C developers can adapt quickly to a new Objective-C API ! The point is that yeah , iPhone may not get as many " general " developers as the Android , but is that really Apple 's goal ?
Apple is doing the same thing they did with the iPod - cross-selling !
Part of why I find the iPhone useful personally is because the apps have a similar ideology to the apps I use on my Macbook Pro .
A lot of popular apps for Mac have syncing versions that are ran on the iPhone .
This applies to some cross platform stuff too , a lot of it starts on Mac , then eventually they port it to PC after they have an iPhone app.So no , Apple does n't benefit from a huge Java community , they benefit from the extremely \ _LOYAL \ _ objective-c community , which since OpenStep is not too popular , is pretty much entirely Apple-centric .</tokentext>
<sentencetext>Yeah, I thought that was funny, but the other big thing is that they're missing the point.Yes, Java developers can adapt quickly to a new Java API, surprise!The iPhone runs a version of Cocoa and you write that in ObjC, just like...every other Apple system!
So guess what?
Objective-C developers can adapt quickly to a new Objective-C API!The point is that yeah, iPhone may not get as many "general" developers as the Android, but is that really Apple's goal?
Apple is doing the same thing they did with the iPod - cross-selling!
Part of why I find the iPhone useful personally is because the apps have a similar ideology to the apps I use on my Macbook Pro.
A lot of popular apps for Mac have syncing versions that are ran on the iPhone.
This applies to some cross platform stuff too, a lot of it starts on Mac, then eventually they port it to PC after they have an iPhone app.So no, Apple doesn't benefit from a huge Java community, they benefit from the extremely \_LOYAL\_ objective-c community, which since OpenStep is not too popular, is pretty much entirely Apple-centric.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366298</id>
	<title>Re:When will we learn...</title>
	<author>Anonymous</author>
	<datestamp>1267716780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>That's where companies like HTC come in and build something like SenseUI for WinMo and Android. It <i>is</i> a superior UI (both platforms). And the best concepts are getting migrated back to Android's core.
<br>
<br>
And that's why Apple is suing...Hmmm...</htmltext>
<tokenext>That 's where companies like HTC come in and build something like SenseUI for WinMo and Android .
It is a superior UI ( both platforms ) .
And the best concepts are getting migrated back to Android 's core .
And that 's why Apple is suing...Hmmm.. .</tokentext>
<sentencetext>That's where companies like HTC come in and build something like SenseUI for WinMo and Android.
It is a superior UI (both platforms).
And the best concepts are getting migrated back to Android's core.
And that's why Apple is suing...Hmmm...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364058</id>
	<title>Re:Developers Developers Developers</title>
	<author>zuperduperman</author>
	<datestamp>1267703340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You should definitely get an iPhone - they are designed to work even for people with severely compromised logic such as yourself.

Good at X does not imply Bad at Y.</htmltext>
<tokenext>You should definitely get an iPhone - they are designed to work even for people with severely compromised logic such as yourself .
Good at X does not imply Bad at Y .</tokentext>
<sentencetext>You should definitely get an iPhone - they are designed to work even for people with severely compromised logic such as yourself.
Good at X does not imply Bad at Y.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364766</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>MrCrassic</author>
	<datestamp>1267706220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And 150\% of statistics are made up on the spot.</p><p>Pandora for the iPhone is so well-written, it's practically a secondary music application for many folks. Many of the popular games on there work pretty well (and are lots of fun too!) and several of the applications I've downloaded have been pretty high-quality (read: few crashes, all of which are related to Safari hogging up memory and the memory being way too limited in the first place). I would be skeptical of thinking iPhone apps are pretty crappy when many, many people have at least four pages worth of apps on their phones.</p></htmltext>
<tokenext>And 150 \ % of statistics are made up on the spot.Pandora for the iPhone is so well-written , it 's practically a secondary music application for many folks .
Many of the popular games on there work pretty well ( and are lots of fun too !
) and several of the applications I 've downloaded have been pretty high-quality ( read : few crashes , all of which are related to Safari hogging up memory and the memory being way too limited in the first place ) .
I would be skeptical of thinking iPhone apps are pretty crappy when many , many people have at least four pages worth of apps on their phones .</tokentext>
<sentencetext>And 150\% of statistics are made up on the spot.Pandora for the iPhone is so well-written, it's practically a secondary music application for many folks.
Many of the popular games on there work pretty well (and are lots of fun too!
) and several of the applications I've downloaded have been pretty high-quality (read: few crashes, all of which are related to Safari hogging up memory and the memory being way too limited in the first place).
I would be skeptical of thinking iPhone apps are pretty crappy when many, many people have at least four pages worth of apps on their phones.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367488</id>
	<title>Re:meh</title>
	<author>Anonymous</author>
	<datestamp>1267725900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>But not java or xcode</p></htmltext>
<tokenext>But not java or xcode</tokentext>
<sentencetext>But not java or xcode</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363998</id>
	<title>Re:No it will not</title>
	<author>Anonymous</author>
	<datestamp>1267703040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And to top that, its not real Java but the embedded/mobile version so your server-side entierprise java bean based app will just not work. Sure, your java devs will be familiar with the language, but frankly, they're all converting themselves to C# nowadays.</p><p>I always thought Android's Dalvik VM was a mistake - they alienated the native C/C++ developers who might have jumped from Symbian to it, and alienated new programmers who think that Java is a lagacy language from the 80s. They'd have been better advised to write a python compiler and use that instead, as long as they allow C library code. In fact the whole Android environment should have been written as C libraries that any language could access without restriction - then you'd get devs from all over using it.</p></htmltext>
<tokenext>And to top that , its not real Java but the embedded/mobile version so your server-side entierprise java bean based app will just not work .
Sure , your java devs will be familiar with the language , but frankly , they 're all converting themselves to C # nowadays.I always thought Android 's Dalvik VM was a mistake - they alienated the native C/C + + developers who might have jumped from Symbian to it , and alienated new programmers who think that Java is a lagacy language from the 80s .
They 'd have been better advised to write a python compiler and use that instead , as long as they allow C library code .
In fact the whole Android environment should have been written as C libraries that any language could access without restriction - then you 'd get devs from all over using it .</tokentext>
<sentencetext>And to top that, its not real Java but the embedded/mobile version so your server-side entierprise java bean based app will just not work.
Sure, your java devs will be familiar with the language, but frankly, they're all converting themselves to C# nowadays.I always thought Android's Dalvik VM was a mistake - they alienated the native C/C++ developers who might have jumped from Symbian to it, and alienated new programmers who think that Java is a lagacy language from the 80s.
They'd have been better advised to write a python compiler and use that instead, as long as they allow C library code.
In fact the whole Android environment should have been written as C libraries that any language could access without restriction - then you'd get devs from all over using it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365838</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>ardor</author>
	<datestamp>1267713360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Unfortunately, Java is a backwards language with zero interesting features whatsoever. The C++ you seemingly abolish allows degrees of polymorphism and modularity Java will never, ever reach. No, I am not talking about low-level C hacking. Look up generic programming in C++, for starters. Or the functional stuff you can do in C#. Or anything you can do in Haskell, which might be an academic language, but is the ultimate eye opener regarding the essential features Java lacks, such as a proper lambda, closures, first class functions, "real" generics. (Anonymous classes are only a very rough approximation to the first two.)</p><p>Yes, I have worked with Java for real. If possible, I use C++ or C# instead. Or Python, Ruby, Lua,<nobr> <wbr></nobr>... almost any other language out there is more powerful than Java these days. Note that I am deliberately not including the virtual machine or the standard library in this - I am talking about the language only.</p></htmltext>
<tokenext>Unfortunately , Java is a backwards language with zero interesting features whatsoever .
The C + + you seemingly abolish allows degrees of polymorphism and modularity Java will never , ever reach .
No , I am not talking about low-level C hacking .
Look up generic programming in C + + , for starters .
Or the functional stuff you can do in C # .
Or anything you can do in Haskell , which might be an academic language , but is the ultimate eye opener regarding the essential features Java lacks , such as a proper lambda , closures , first class functions , " real " generics .
( Anonymous classes are only a very rough approximation to the first two .
) Yes , I have worked with Java for real .
If possible , I use C + + or C # instead .
Or Python , Ruby , Lua , ... almost any other language out there is more powerful than Java these days .
Note that I am deliberately not including the virtual machine or the standard library in this - I am talking about the language only .</tokentext>
<sentencetext>Unfortunately, Java is a backwards language with zero interesting features whatsoever.
The C++ you seemingly abolish allows degrees of polymorphism and modularity Java will never, ever reach.
No, I am not talking about low-level C hacking.
Look up generic programming in C++, for starters.
Or the functional stuff you can do in C#.
Or anything you can do in Haskell, which might be an academic language, but is the ultimate eye opener regarding the essential features Java lacks, such as a proper lambda, closures, first class functions, "real" generics.
(Anonymous classes are only a very rough approximation to the first two.
)Yes, I have worked with Java for real.
If possible, I use C++ or C# instead.
Or Python, Ruby, Lua, ... almost any other language out there is more powerful than Java these days.
Note that I am deliberately not including the virtual machine or the standard library in this - I am talking about the language only.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364412</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365250</id>
	<title>Re:wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267708920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Why?  Why would I want to do this?  Why on earth would I ever want to buy, and cary around, yet another device when one that I already have a fully capable playing one of these games... if one of these games is what I to play?</p></htmltext>
<tokenext>Why ?
Why would I want to do this ?
Why on earth would I ever want to buy , and cary around , yet another device when one that I already have a fully capable playing one of these games... if one of these games is what I to play ?</tokentext>
<sentencetext>Why?
Why would I want to do this?
Why on earth would I ever want to buy, and cary around, yet another device when one that I already have a fully capable playing one of these games... if one of these games is what I to play?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366812</id>
	<title>Re:No it will not</title>
	<author>jmrives</author>
	<datestamp>1267720980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This is true. I have been developing a game app for Android. So, I am quite familiar with the environment. The Java implementation for Android is not complete. The one area that was missing for me is the RMI (remote method invocation for you non-java folks). That said, I have found the development experience to be a good one. I have nearly 15 years of Java development experience. I know a good development environment when I see one.</htmltext>
<tokenext>This is true .
I have been developing a game app for Android .
So , I am quite familiar with the environment .
The Java implementation for Android is not complete .
The one area that was missing for me is the RMI ( remote method invocation for you non-java folks ) .
That said , I have found the development experience to be a good one .
I have nearly 15 years of Java development experience .
I know a good development environment when I see one .</tokentext>
<sentencetext>This is true.
I have been developing a game app for Android.
So, I am quite familiar with the environment.
The Java implementation for Android is not complete.
The one area that was missing for me is the RMI (remote method invocation for you non-java folks).
That said, I have found the development experience to be a good one.
I have nearly 15 years of Java development experience.
I know a good development environment when I see one.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364370</id>
	<title>Are you kidding me???</title>
	<author>thetartanavenger</author>
	<datestamp>1267704540000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>The pure Java foundation of Android</p></div><p>Android is not java. Yes it has java aspects but it is not java! It's bits of java with a customized Android API.It doesn't even run a normal JVM, it runs the Dalvik VM.</p><p><div class="quote"><p>Not only that, but all of the code from other Java programs will run on your Android phone</p></div><p>Seriously, no. Just... no. Try compiling a program that uses Swing, AWT or javax stuff.</p><p>Don't get me wrong, I really like Android and hate iPhones. I have a G1 (lacking on RAM as much as it is). I've programmed for android although for fun, not the marketplace. I've even made my own ROM, again for fun. But claiming Android is Java and that everything that Java can do Android can also do natively is just naive</p></div>
	</htmltext>
<tokenext>The pure Java foundation of AndroidAndroid is not java .
Yes it has java aspects but it is not java !
It 's bits of java with a customized Android API.It does n't even run a normal JVM , it runs the Dalvik VM.Not only that , but all of the code from other Java programs will run on your Android phoneSeriously , no .
Just... no .
Try compiling a program that uses Swing , AWT or javax stuff.Do n't get me wrong , I really like Android and hate iPhones .
I have a G1 ( lacking on RAM as much as it is ) .
I 've programmed for android although for fun , not the marketplace .
I 've even made my own ROM , again for fun .
But claiming Android is Java and that everything that Java can do Android can also do natively is just naive</tokentext>
<sentencetext>The pure Java foundation of AndroidAndroid is not java.
Yes it has java aspects but it is not java!
It's bits of java with a customized Android API.It doesn't even run a normal JVM, it runs the Dalvik VM.Not only that, but all of the code from other Java programs will run on your Android phoneSeriously, no.
Just... no.
Try compiling a program that uses Swing, AWT or javax stuff.Don't get me wrong, I really like Android and hate iPhones.
I have a G1 (lacking on RAM as much as it is).
I've programmed for android although for fun, not the marketplace.
I've even made my own ROM, again for fun.
But claiming Android is Java and that everything that Java can do Android can also do natively is just naive
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369938</id>
	<title>Re:meh</title>
	<author>mcvos</author>
	<datestamp>1267798320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>the nokia n900 + maemo allows multiple languages and frameworks (x11 gtk qt sdl gles and whatever else you can throw at it) to peacefully coexist together<nobr> <wbr></nobr>:)</p><p>don't take my word for it though, i'm biased</p></div><p>I'm not. I didn't buy an n900 because I expected a lot more support for Android (and because a Milestone just looks so much better), but Maemo is definitely the ultimate geek smartphone OS. And you're really the owner of your own system: you're root, unlike on Android or the iPhone.</p></div>
	</htmltext>
<tokenext>the nokia n900 + maemo allows multiple languages and frameworks ( x11 gtk qt sdl gles and whatever else you can throw at it ) to peacefully coexist together : ) do n't take my word for it though , i 'm biasedI 'm not .
I did n't buy an n900 because I expected a lot more support for Android ( and because a Milestone just looks so much better ) , but Maemo is definitely the ultimate geek smartphone OS .
And you 're really the owner of your own system : you 're root , unlike on Android or the iPhone .</tokentext>
<sentencetext>the nokia n900 + maemo allows multiple languages and frameworks (x11 gtk qt sdl gles and whatever else you can throw at it) to peacefully coexist together :)don't take my word for it though, i'm biasedI'm not.
I didn't buy an n900 because I expected a lot more support for Android (and because a Milestone just looks so much better), but Maemo is definitely the ultimate geek smartphone OS.
And you're really the owner of your own system: you're root, unlike on Android or the iPhone.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365418</id>
	<title>Re:wake me up when it catches up</title>
	<author>mdwh2</author>
	<datestamp>1267710060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>you know that the platform is popular.</i></p><p>Non sequitur.</p><p>I know a platform is popular, by looking at the sales figures and market share. In the mobile market, that's companies like Nokia, not Apple.</p></htmltext>
<tokenext>you know that the platform is popular.Non sequitur.I know a platform is popular , by looking at the sales figures and market share .
In the mobile market , that 's companies like Nokia , not Apple .</tokentext>
<sentencetext>you know that the platform is popular.Non sequitur.I know a platform is popular, by looking at the sales figures and market share.
In the mobile market, that's companies like Nokia, not Apple.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367454</id>
	<title>Knock Knock...</title>
	<author>Anonymous</author>
	<datestamp>1267725480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Knock Knock...</p><p>Whose there?</p><p>[long pause]</p><p>Java</p><p>[longer pause]</p><p>Java (running on phone)</p></htmltext>
<tokenext>Knock Knock...Whose there ?
[ long pause ] Java [ longer pause ] Java ( running on phone )</tokentext>
<sentencetext>Knock Knock...Whose there?
[long pause]Java[longer pause]Java (running on phone)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368244</id>
	<title>Re:When will we learn...</title>
	<author>genik76</author>
	<datestamp>1267820760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If there are no developers, there are no programs. And if there are no programs, there are no users.</htmltext>
<tokenext>If there are no developers , there are no programs .
And if there are no programs , there are no users .</tokentext>
<sentencetext>If there are no developers, there are no programs.
And if there are no programs, there are no users.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363760</id>
	<title>Use "em" not "px" when defining the UI</title>
	<author>Anonymous</author>
	<datestamp>1267701960000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>To those about to complain that screen resolution differences makes developing for android harder, then try using a UI measurement that does not rely on pixels, like em</p></htmltext>
<tokenext>To those about to complain that screen resolution differences makes developing for android harder , then try using a UI measurement that does not rely on pixels , like em</tokentext>
<sentencetext>To those about to complain that screen resolution differences makes developing for android harder, then try using a UI measurement that does not rely on pixels, like em</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369428</id>
	<title>Re:Windows Mobile</title>
	<author>Xest</author>
	<datestamp>1267792920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well yeah, you're actually right, as it happens, Windows Mobile really is MUCH simpler to develop for than any other phone platform because you get to use Visual Studio and<nobr> <wbr></nobr>.NET. Just because WinMo itself has been a bit crap for it's past few releases, doesn't mean it doesn't beat the iPhone and Android in terms of ease of development.</p><p>I think you're under the assumption that he's saying Android is better than the iPhone overall because it's easier to develop for, he's not, he's saying it's better than the iPhone for developers who actually want to write apps for that phone, which is absolutely true, just as as you say, Windows Mobile is indeed even better again for developers to develop for.</p></htmltext>
<tokenext>Well yeah , you 're actually right , as it happens , Windows Mobile really is MUCH simpler to develop for than any other phone platform because you get to use Visual Studio and .NET .
Just because WinMo itself has been a bit crap for it 's past few releases , does n't mean it does n't beat the iPhone and Android in terms of ease of development.I think you 're under the assumption that he 's saying Android is better than the iPhone overall because it 's easier to develop for , he 's not , he 's saying it 's better than the iPhone for developers who actually want to write apps for that phone , which is absolutely true , just as as you say , Windows Mobile is indeed even better again for developers to develop for .</tokentext>
<sentencetext>Well yeah, you're actually right, as it happens, Windows Mobile really is MUCH simpler to develop for than any other phone platform because you get to use Visual Studio and .NET.
Just because WinMo itself has been a bit crap for it's past few releases, doesn't mean it doesn't beat the iPhone and Android in terms of ease of development.I think you're under the assumption that he's saying Android is better than the iPhone overall because it's easier to develop for, he's not, he's saying it's better than the iPhone for developers who actually want to write apps for that phone, which is absolutely true, just as as you say, Windows Mobile is indeed even better again for developers to develop for.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364794</id>
	<title>Re:Windows Mobile</title>
	<author>MrCrassic</author>
	<datestamp>1267706400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But if you read the article, you would see that he goes in depth about actually developing for both platforms. Windows Mobile was actually pretty good on that front, but wouldn't be better than Android because:</p><ol><li>Most of the core WinMo libraries are on Windows,</li><li>It's not open, and</li><li>It's pretty unreliable as an OS in comparison to the others on similar hardware.</li></ol></htmltext>
<tokenext>But if you read the article , you would see that he goes in depth about actually developing for both platforms .
Windows Mobile was actually pretty good on that front , but would n't be better than Android because : Most of the core WinMo libraries are on Windows,It 's not open , andIt 's pretty unreliable as an OS in comparison to the others on similar hardware .</tokentext>
<sentencetext>But if you read the article, you would see that he goes in depth about actually developing for both platforms.
Windows Mobile was actually pretty good on that front, but wouldn't be better than Android because:Most of the core WinMo libraries are on Windows,It's not open, andIt's pretty unreliable as an OS in comparison to the others on similar hardware.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367256</id>
	<title>Re:Java as an "advantage?"</title>
	<author>Skreems</author>
	<datestamp>1267724040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Objective-C has advantages, such as that it is compiled.</p></div></blockquote><p>
I would heavily dispute this. Yes, Objective-C is compiled, while Java is "only" byte-code. However, Java performance has improved dramatically in the past 10 years since the "Java is slow" meme started, while Objective-C still uses an amazingly slow message handler evaluation mechanism to resolve virtual function calls, instead of anything resembling a real OOP mechanism. Nice and flexible if you know how to use it, but a lot more potential for performance pitfalls if you don't have a really good handle on how to organize your classes.</p></div>
	</htmltext>
<tokenext>Objective-C has advantages , such as that it is compiled .
I would heavily dispute this .
Yes , Objective-C is compiled , while Java is " only " byte-code .
However , Java performance has improved dramatically in the past 10 years since the " Java is slow " meme started , while Objective-C still uses an amazingly slow message handler evaluation mechanism to resolve virtual function calls , instead of anything resembling a real OOP mechanism .
Nice and flexible if you know how to use it , but a lot more potential for performance pitfalls if you do n't have a really good handle on how to organize your classes .</tokentext>
<sentencetext>Objective-C has advantages, such as that it is compiled.
I would heavily dispute this.
Yes, Objective-C is compiled, while Java is "only" byte-code.
However, Java performance has improved dramatically in the past 10 years since the "Java is slow" meme started, while Objective-C still uses an amazingly slow message handler evaluation mechanism to resolve virtual function calls, instead of anything resembling a real OOP mechanism.
Nice and flexible if you know how to use it, but a lot more potential for performance pitfalls if you don't have a really good handle on how to organize your classes.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367628</id>
	<title>Denta Smile Md</title>
	<author>jaffredi</author>
	<datestamp>1267727100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext> I had the same problem with my iphone pearl and was told it was because of memory shortage. Like when you go on the internet alot or something,
<a href="http://ezinearticles.com/?Denta-Smile-MD-Review&amp;id=3852536" title="ezinearticles.com" rel="nofollow">Denta Smile Md</a> [ezinearticles.com]</htmltext>
<tokenext>I had the same problem with my iphone pearl and was told it was because of memory shortage .
Like when you go on the internet alot or something , Denta Smile Md [ ezinearticles.com ]</tokentext>
<sentencetext> I had the same problem with my iphone pearl and was told it was because of memory shortage.
Like when you go on the internet alot or something,
Denta Smile Md [ezinearticles.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366404</id>
	<title>Re:wake me up when it catches up</title>
	<author>VocationalZero</author>
	<datestamp>1267717800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Also, have you seen the relative difference in price for Nintendo DS and Sony PSP games versus the ones for the phones?</p></div><p>And have you seen the relative difference in quality for Nintendo DS and Sony PSP games versus the ones for the phones?</p></div>
	</htmltext>
<tokenext>Also , have you seen the relative difference in price for Nintendo DS and Sony PSP games versus the ones for the phones ? And have you seen the relative difference in quality for Nintendo DS and Sony PSP games versus the ones for the phones ?</tokentext>
<sentencetext>Also, have you seen the relative difference in price for Nintendo DS and Sony PSP games versus the ones for the phones?And have you seen the relative difference in quality for Nintendo DS and Sony PSP games versus the ones for the phones?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365128</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365646</id>
	<title>LOL.  Living in the past, are we?</title>
	<author>Anonymous</author>
	<datestamp>1267711680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><i>Objective-C has advantages, such as that it is compiled.</i></p><p>Objective-C also has disadvantages, such as that it is compiled, and also such that it is a much more difficult language to learn and master than Java, and such as that it is a proprietary language limited to one platform and one platform only.  With Java, you can learn a single language and write code for *EVERYTHING*.</p><p><i>X-Code is a purpose-built, clean-sheet IDE that may lack a few power features found in Eclipse, and Eclipse has numerous plug-ins, but Eclipse also has a pretty diabolical UI, especially compared to software from Apple.</i></p><p>Yes, right, X-Code is "better" simply because it is from apple.  Never mind that it works almost identically to Eclipse, no sir!  Eclipse is "diabolical", which is why millions of developers use it every single fucking day.  You Apple zealots really need to get out more.</p></htmltext>
<tokenext>Objective-C has advantages , such as that it is compiled.Objective-C also has disadvantages , such as that it is compiled , and also such that it is a much more difficult language to learn and master than Java , and such as that it is a proprietary language limited to one platform and one platform only .
With Java , you can learn a single language and write code for * EVERYTHING * .X-Code is a purpose-built , clean-sheet IDE that may lack a few power features found in Eclipse , and Eclipse has numerous plug-ins , but Eclipse also has a pretty diabolical UI , especially compared to software from Apple.Yes , right , X-Code is " better " simply because it is from apple .
Never mind that it works almost identically to Eclipse , no sir !
Eclipse is " diabolical " , which is why millions of developers use it every single fucking day .
You Apple zealots really need to get out more .</tokentext>
<sentencetext>Objective-C has advantages, such as that it is compiled.Objective-C also has disadvantages, such as that it is compiled, and also such that it is a much more difficult language to learn and master than Java, and such as that it is a proprietary language limited to one platform and one platform only.
With Java, you can learn a single language and write code for *EVERYTHING*.X-Code is a purpose-built, clean-sheet IDE that may lack a few power features found in Eclipse, and Eclipse has numerous plug-ins, but Eclipse also has a pretty diabolical UI, especially compared to software from Apple.Yes, right, X-Code is "better" simply because it is from apple.
Never mind that it works almost identically to Eclipse, no sir!
Eclipse is "diabolical", which is why millions of developers use it every single fucking day.
You Apple zealots really need to get out more.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365040</id>
	<title>Re:Not as fast?</title>
	<author>shutdown -p now</author>
	<datestamp>1267707720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code?</p></div><p>My cellphone is from 2007 (Nokia 6300), and it wasn't considered a smartphone even back then. However, it happily runs <a href="http://www.galaxy-on-fire.com/eng/index.html" title="galaxy-on-fire.com">Java 3D games</a> [galaxy-on-fire.com] - granted, the graphics is rather primitive, and more reminiscent of what we saw on PCs in mid-to-late 90s, but still.</p></div>
	</htmltext>
<tokenext>Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code ? My cellphone is from 2007 ( Nokia 6300 ) , and it was n't considered a smartphone even back then .
However , it happily runs Java 3D games [ galaxy-on-fire.com ] - granted , the graphics is rather primitive , and more reminiscent of what we saw on PCs in mid-to-late 90s , but still .</tokentext>
<sentencetext>Are there any mobile devices out there that can really handle even moderately complex / processor intensive Java code?My cellphone is from 2007 (Nokia 6300), and it wasn't considered a smartphone even back then.
However, it happily runs Java 3D games [galaxy-on-fire.com] - granted, the graphics is rather primitive, and more reminiscent of what we saw on PCs in mid-to-late 90s, but still.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368272</id>
	<title>Re:amazing!</title>
	<author>CharlyFoxtrot</author>
	<datestamp>1267820940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You know I can't count the number of times I sat before an "enterprise" java application and thought to myself "I wish these people were making the software that runs on my phone !" Yeah they're <a href="http://en.wikipedia.org/wiki/Real\_Programmer" title="wikipedia.org">REAL programmers</a> [wikipedia.org] not nansy pansy "designers" like those iPhone types.</p></htmltext>
<tokenext>You know I ca n't count the number of times I sat before an " enterprise " java application and thought to myself " I wish these people were making the software that runs on my phone !
" Yeah they 're REAL programmers [ wikipedia.org ] not nansy pansy " designers " like those iPhone types .</tokentext>
<sentencetext>You know I can't count the number of times I sat before an "enterprise" java application and thought to myself "I wish these people were making the software that runs on my phone !
" Yeah they're REAL programmers [wikipedia.org] not nansy pansy "designers" like those iPhone types.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363792</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363906</id>
	<title>JavaFX</title>
	<author>Anonymous</author>
	<datestamp>1267702620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'll buy an Android phone when it runs JavaFX.</p></htmltext>
<tokenext>I 'll buy an Android phone when it runs JavaFX .</tokentext>
<sentencetext>I'll buy an Android phone when it runs JavaFX.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364900</id>
	<title>Re:wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267706940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Really? Productivity defined as?</p><p>Would an excel spreadsheet render properly on a Droid? Do you code in C# on the Nokia? Pray tell, what forms of productivity do you increase, Almighty one?</p></htmltext>
<tokenext>Really ?
Productivity defined as ? Would an excel spreadsheet render properly on a Droid ?
Do you code in C # on the Nokia ?
Pray tell , what forms of productivity do you increase , Almighty one ?</tokentext>
<sentencetext>Really?
Productivity defined as?Would an excel spreadsheet render properly on a Droid?
Do you code in C# on the Nokia?
Pray tell, what forms of productivity do you increase, Almighty one?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363792</id>
	<title>amazing!</title>
	<author>Anonymous</author>
	<datestamp>1267702140000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>After reading the article, I was able to port my entire Java repository to Android in just a few minutes.  Of course, that consists of three versions of "Hello, world!"</p></htmltext>
<tokenext>After reading the article , I was able to port my entire Java repository to Android in just a few minutes .
Of course , that consists of three versions of " Hello , world !
"</tokentext>
<sentencetext>After reading the article, I was able to port my entire Java repository to Android in just a few minutes.
Of course, that consists of three versions of "Hello, world!
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828</id>
	<title>Re:Use "em" not "px" when defining the UI</title>
	<author>Anonymous</author>
	<datestamp>1267702320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>To those about to complain that screen resolution differences makes developing for android harder, then try using a UI measurement that does not rely on pixels, like em</p></div><p>Incidentally bitmaps that use em have not been invented yet. Vectors are not good for everything, and may take more power to render on the fly.</p><p>Also, em solves exactly nothing about how much content can you fit on a display before it becomes unreadable, a problem you may get if you treat DPI as a free variable. Oh and it also doesn't factor in display ratio, unless you think squashing things is the way to go.</p></div>
	</htmltext>
<tokenext>To those about to complain that screen resolution differences makes developing for android harder , then try using a UI measurement that does not rely on pixels , like emIncidentally bitmaps that use em have not been invented yet .
Vectors are not good for everything , and may take more power to render on the fly.Also , em solves exactly nothing about how much content can you fit on a display before it becomes unreadable , a problem you may get if you treat DPI as a free variable .
Oh and it also does n't factor in display ratio , unless you think squashing things is the way to go .</tokentext>
<sentencetext>To those about to complain that screen resolution differences makes developing for android harder, then try using a UI measurement that does not rely on pixels, like emIncidentally bitmaps that use em have not been invented yet.
Vectors are not good for everything, and may take more power to render on the fly.Also, em solves exactly nothing about how much content can you fit on a display before it becomes unreadable, a problem you may get if you treat DPI as a free variable.
Oh and it also doesn't factor in display ratio, unless you think squashing things is the way to go.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363760</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364454</id>
	<title>Platform choice and Cost</title>
	<author>Ewlkaz</author>
	<datestamp>1267704900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Developing for the iPhone requires OSX. Publishing an app to the market requires a $99 license. App Store rules are quite stringent.

Developing for the Android Platform requires Windows, Linux or OSX. Publishing an app costs nothing. Market rules are a lot less stringent than App Store.

iPhone OS is closed.
Android OS is open source allowing developers to support phones that hardware companies have dropped.</htmltext>
<tokenext>Developing for the iPhone requires OSX .
Publishing an app to the market requires a $ 99 license .
App Store rules are quite stringent .
Developing for the Android Platform requires Windows , Linux or OSX .
Publishing an app costs nothing .
Market rules are a lot less stringent than App Store .
iPhone OS is closed .
Android OS is open source allowing developers to support phones that hardware companies have dropped .</tokentext>
<sentencetext>Developing for the iPhone requires OSX.
Publishing an app to the market requires a $99 license.
App Store rules are quite stringent.
Developing for the Android Platform requires Windows, Linux or OSX.
Publishing an app costs nothing.
Market rules are a lot less stringent than App Store.
iPhone OS is closed.
Android OS is open source allowing developers to support phones that hardware companies have dropped.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364322</id>
	<title>Re:meh</title>
	<author>Microlith</author>
	<datestamp>1267704420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It does?</p><p>Can you point out the binary only 3rd party module?</p></htmltext>
<tokenext>It does ? Can you point out the binary only 3rd party module ?</tokentext>
<sentencetext>It does?Can you point out the binary only 3rd party module?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364176</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363804</id>
	<title>lol</title>
	<author>Anonymous</author>
	<datestamp>1267702200000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext>if java is your secret, you should probably kill yourself.</htmltext>
<tokenext>if java is your secret , you should probably kill yourself .</tokentext>
<sentencetext>if java is your secret, you should probably kill yourself.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368252</id>
	<title>Re:When will we learn...</title>
	<author>aCC</author>
	<datestamp>1267820760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's so true! I <b>LOVE</b> my N900 (even more open than Android), mainly because of the endless possibilities of what I can do with it. Freedom to do anything with your phone/computer rocks.</p><p>But in the current state of its software I would <b>NEVER</b> recommend it to my wife or family. They are so much better served by an iphone at the moment because it just works. Maybe once all the developers have fixed the missing features of the N900 it starts to get interesting for non-developers (probably in the 3rd generation N900 like with the iphone). To me the current software of N900 feels like KDE 4.0 felt. Ready for developers but really lacking for users.</p><p>The N900 is like a DIY set of a Ferrari. Not much use if you don't spend a lot of time putting it all together and fixing what needs fixed.</p></htmltext>
<tokenext>That 's so true !
I LOVE my N900 ( even more open than Android ) , mainly because of the endless possibilities of what I can do with it .
Freedom to do anything with your phone/computer rocks.But in the current state of its software I would NEVER recommend it to my wife or family .
They are so much better served by an iphone at the moment because it just works .
Maybe once all the developers have fixed the missing features of the N900 it starts to get interesting for non-developers ( probably in the 3rd generation N900 like with the iphone ) .
To me the current software of N900 feels like KDE 4.0 felt .
Ready for developers but really lacking for users.The N900 is like a DIY set of a Ferrari .
Not much use if you do n't spend a lot of time putting it all together and fixing what needs fixed .</tokentext>
<sentencetext>That's so true!
I LOVE my N900 (even more open than Android), mainly because of the endless possibilities of what I can do with it.
Freedom to do anything with your phone/computer rocks.But in the current state of its software I would NEVER recommend it to my wife or family.
They are so much better served by an iphone at the moment because it just works.
Maybe once all the developers have fixed the missing features of the N900 it starts to get interesting for non-developers (probably in the 3rd generation N900 like with the iphone).
To me the current software of N900 feels like KDE 4.0 felt.
Ready for developers but really lacking for users.The N900 is like a DIY set of a Ferrari.
Not much use if you don't spend a lot of time putting it all together and fixing what needs fixed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368538</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>kaffiene</author>
	<datestamp>1267781400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What a load of utter crap.  Thats the least logical thing I've seen on slashdot in years, and that's saying a lot</p></htmltext>
<tokenext>What a load of utter crap .
Thats the least logical thing I 've seen on slashdot in years , and that 's saying a lot</tokentext>
<sentencetext>What a load of utter crap.
Thats the least logical thing I've seen on slashdot in years, and that's saying a lot</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364412</id>
	<title>Re:Shitty programmers writing shitty code.</title>
	<author>Anonymous</author>
	<datestamp>1267704780000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Java does not just allow bad programmers to write sloppy code, it also allows good programmers to write better code (than in C/C++ and direct derivatives). Shitty programs are available in all languages. I managed to write a shit application in Lua in a minute flat. How difficult is it to grasp this concept? Do you really want a programming language that makes it harder to write manageable code, on purpose?</p><p>I'm getting sick of this argument. Most of my esteemed C++ colleagues like Java once they've actually tried it out for real. Unfortunately we don't always get Java libs for the hardware we are using.</p></htmltext>
<tokenext>Java does not just allow bad programmers to write sloppy code , it also allows good programmers to write better code ( than in C/C + + and direct derivatives ) .
Shitty programs are available in all languages .
I managed to write a shit application in Lua in a minute flat .
How difficult is it to grasp this concept ?
Do you really want a programming language that makes it harder to write manageable code , on purpose ? I 'm getting sick of this argument .
Most of my esteemed C + + colleagues like Java once they 've actually tried it out for real .
Unfortunately we do n't always get Java libs for the hardware we are using .</tokentext>
<sentencetext>Java does not just allow bad programmers to write sloppy code, it also allows good programmers to write better code (than in C/C++ and direct derivatives).
Shitty programs are available in all languages.
I managed to write a shit application in Lua in a minute flat.
How difficult is it to grasp this concept?
Do you really want a programming language that makes it harder to write manageable code, on purpose?I'm getting sick of this argument.
Most of my esteemed C++ colleagues like Java once they've actually tried it out for real.
Unfortunately we don't always get Java libs for the hardware we are using.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364990</id>
	<title>Ha.</title>
	<author>mbessey</author>
	<datestamp>1267707480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>&gt; This has thankfully prevented it from becoming the language of choice in major outsourcing and offshoring destinations<br>&gt; like India, Pakistan and Vietnam</p><p>A quick perusal of iPhone-related questions on Apple's discussion boards, or on stackoverflow.com, would quickly cure you of this belief. A lot of people at the "bang the rocks together" level of expertise are trying to develop iPhone apps. People (and companies) go where the opportunity is.</p><p>I've been approached by one India-based organization to act as a "Public face" for them here in the states, so I know there are shops full of inexperienced iPhone developers in India who are pitching US companies on developing their "mobile strategy" for them.<br>
&nbsp;</p></htmltext>
<tokenext>&gt; This has thankfully prevented it from becoming the language of choice in major outsourcing and offshoring destinations &gt; like India , Pakistan and VietnamA quick perusal of iPhone-related questions on Apple 's discussion boards , or on stackoverflow.com , would quickly cure you of this belief .
A lot of people at the " bang the rocks together " level of expertise are trying to develop iPhone apps .
People ( and companies ) go where the opportunity is.I 've been approached by one India-based organization to act as a " Public face " for them here in the states , so I know there are shops full of inexperienced iPhone developers in India who are pitching US companies on developing their " mobile strategy " for them .
 </tokentext>
<sentencetext>&gt; This has thankfully prevented it from becoming the language of choice in major outsourcing and offshoring destinations&gt; like India, Pakistan and VietnamA quick perusal of iPhone-related questions on Apple's discussion boards, or on stackoverflow.com, would quickly cure you of this belief.
A lot of people at the "bang the rocks together" level of expertise are trying to develop iPhone apps.
People (and companies) go where the opportunity is.I've been approached by one India-based organization to act as a "Public face" for them here in the states, so I know there are shops full of inexperienced iPhone developers in India who are pitching US companies on developing their "mobile strategy" for them.
 </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365106</id>
	<title>Re:wake me up when it catches up</title>
	<author>Anonymous</author>
	<datestamp>1267708020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Some of us carry smartphones to increase productivity, not play video games on a 4 inch screen.<br>If grand theft auto on your phone is a selling point... god help us all.<br>If you want to play games, buy one of those portable game widget things that Nintendo or Sony sells.</p></div><p>Spoken like someone who sees no problem carrying a, say, PSP and a phone at the same time, and someone who has never used public transportation.</p></div>
	</htmltext>
<tokenext>Some of us carry smartphones to increase productivity , not play video games on a 4 inch screen.If grand theft auto on your phone is a selling point... god help us all.If you want to play games , buy one of those portable game widget things that Nintendo or Sony sells.Spoken like someone who sees no problem carrying a , say , PSP and a phone at the same time , and someone who has never used public transportation .</tokentext>
<sentencetext>Some of us carry smartphones to increase productivity, not play video games on a 4 inch screen.If grand theft auto on your phone is a selling point... god help us all.If you want to play games, buy one of those portable game widget things that Nintendo or Sony sells.Spoken like someone who sees no problem carrying a, say, PSP and a phone at the same time, and someone who has never used public transportation.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364728
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_68</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363944
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364108
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369532
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31374664
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365076
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366298
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_69</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365376
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365720
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_70</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31371124
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364794
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_66</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364900
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365480
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_71</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365040
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364690
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364420
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364050
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365864
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368130
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364722
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365200
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365566
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367256
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365418
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368252
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365204
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367906
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365594
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363760
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367200
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365888
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364290
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31382622
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364412
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365838
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31370546
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364622
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31370894
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363998
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364262
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365250
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367488
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369240
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364058
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368250
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365182
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363792
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368272
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365676
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368256
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364106
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365614
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368538
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364784
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_67</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367252
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363760
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365316
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366812
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368244
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365308
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364440
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364990
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31406962
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364190
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369428
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369332
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365324
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364622
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31373266
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365128
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366404
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369938
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_72</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363766
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364746
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365646
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366972
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367582
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366244
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368154
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365106
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364092
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363760
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367446
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364176
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364322
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_04_2039212_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365216
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363792
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368272
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364622
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31373266
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31370894
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363800
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367488
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365720
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365200
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365566
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368130
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364176
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364322
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368256
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369938
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365676
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363758
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365324
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367906
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365376
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365594
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363940
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365076
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369428
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364794
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363906
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363766
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364746
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363918
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368154
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369240
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364058
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31371124
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363760
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363828
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365316
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367446
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367200
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363846
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363976
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364420
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365888
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364766
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364784
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364440
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364612
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31382622
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364108
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364412
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365838
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31370546
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368538
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364990
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364728
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365340
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368516
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363868
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368250
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364690
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365864
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364190
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366812
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363998
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364262
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367252
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363930
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365040
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364092
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369332
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363948
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31406962
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364334
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364900
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365480
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365250
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365128
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366404
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365106
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365182
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365216
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365204
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365418
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366608
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364302
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31369532
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365308
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366972
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31374664
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365646
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367256
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366244
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364644
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368244
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31367582
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31366298
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31368252
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364106
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31365614
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364726
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363798
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364290
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364050
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31363944
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364722
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_04_2039212.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_04_2039212.31364370
</commentlist>
</conversation>
