<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_10_14_0511259</id>
	<title>Game Development On Android</title>
	<author>Soulskill</author>
	<datestamp>1255518840000</datestamp>
	<htmltext>Gamasutra is running an article about <a href="http://www.gamasutra.com/view/feature/4160/developing\_games\_for\_android.php">the state of game development on Android</a>. The author explains some of the strengths and weaknesses of the platform, and makes comparisons to development on the iPhone. Quoting:
<i>"While iPhone apps are written in Objective C, the Android SDK uses relatively more programmer-friendly Java. The iPhone store charges developers $99 a year to distribute their apps, while Android has a one-time $25 fee for developers. And the review process for iPhone apps grows increasingly lengthy &mdash; sometimes weeks or more &mdash; and it's somewhat arcane. Android apps go live as soon as the developer hits the publish button. Google handles the review process post-hoc, and is much more lax in terms of content. ... For now, if a developer decides to implement a game exclusively for a particular smartphone platform, and the choice is between the iPhone and Android, the tradeoff is between trying to get noticed in an incredibly crowded and competitive market where the potential payoff is huge for those at the top, or entering a market with low barriers, little competition, currently low returns, but the possibility of potential growth."</i></htmltext>
<tokenext>Gamasutra is running an article about the state of game development on Android .
The author explains some of the strengths and weaknesses of the platform , and makes comparisons to development on the iPhone .
Quoting : " While iPhone apps are written in Objective C , the Android SDK uses relatively more programmer-friendly Java .
The iPhone store charges developers $ 99 a year to distribute their apps , while Android has a one-time $ 25 fee for developers .
And the review process for iPhone apps grows increasingly lengthy    sometimes weeks or more    and it 's somewhat arcane .
Android apps go live as soon as the developer hits the publish button .
Google handles the review process post-hoc , and is much more lax in terms of content .
... For now , if a developer decides to implement a game exclusively for a particular smartphone platform , and the choice is between the iPhone and Android , the tradeoff is between trying to get noticed in an incredibly crowded and competitive market where the potential payoff is huge for those at the top , or entering a market with low barriers , little competition , currently low returns , but the possibility of potential growth .
"</tokentext>
<sentencetext>Gamasutra is running an article about the state of game development on Android.
The author explains some of the strengths and weaknesses of the platform, and makes comparisons to development on the iPhone.
Quoting:
"While iPhone apps are written in Objective C, the Android SDK uses relatively more programmer-friendly Java.
The iPhone store charges developers $99 a year to distribute their apps, while Android has a one-time $25 fee for developers.
And the review process for iPhone apps grows increasingly lengthy — sometimes weeks or more — and it's somewhat arcane.
Android apps go live as soon as the developer hits the publish button.
Google handles the review process post-hoc, and is much more lax in terms of content.
... For now, if a developer decides to implement a game exclusively for a particular smartphone platform, and the choice is between the iPhone and Android, the tradeoff is between trying to get noticed in an incredibly crowded and competitive market where the potential payoff is huge for those at the top, or entering a market with low barriers, little competition, currently low returns, but the possibility of potential growth.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744219</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>2obvious4u</author>
	<datestamp>1255533060000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext>The key is the carriers.<br>
Verizon has the largest network and subscriber base,
<a href="http://www.verizonwireless.com/b2c/store/controller?item=phoneFirst&amp;action=viewPhoneOverviewByDevice&amp;deviceType=Phones&amp;sortOption=priceSort&amp;lid=//global//phones+and+accessories//cell+phones" title="verizonwireless.com">
but doesn't have any </a> [verizonwireless.com]
<a href="http://www.wired.com/gadgetlab/2009/09/verizon-smartphones/" title="wired.com">good smart phones.</a> [wired.com] <br>
T-mobile has the g1, but T-mobile
<a href="http://etf-settlement.com/" title="etf-settlement.com">is</a> [etf-settlement.com]
<a href="http://news.cnet.com/8301-17938\_105-10241101-1.html" title="cnet.com">a horrible</a> [cnet.com] company.<br>
AT&amp;T has the iphone but it
<a href="http://www.att.com/wireless/iphone/" title="att.com">costs a fortune</a> [att.com] for service.<br>
<br>
The key will be what smart phone takes hold on Verizon; currently it looks like it is going to be an android phone.<br>
<br>
<a href="http://en.wikipedia.org/wiki/Verizon\_Wireless" title="wikipedia.org">Verizon Wireless: 87.7 Million subscribers</a> [wikipedia.org] <br>
<a href="http://en.wikipedia.org/wiki/AT\%26T\_Mobility" title="wikipedia.org">AT&amp;T Mobility: 79.6 Million Subscribers</a> [wikipedia.org] <br>
<a href="http://en.wikipedia.org/wiki/Sprint\_Nextel" title="wikipedia.org">Sprint: 49.3 Million subscribers</a> [wikipedia.org] <br>
<a href="http://en.wikipedia.org/wiki/T-Mobile\_USA" title="wikipedia.org">T-Mobile: 38.2 million subscribers</a> [wikipedia.org] <br>
<br>
Personally I'm waiting for a phone similar to the G1 to be available on the Verizon network.</htmltext>
<tokenext>The key is the carriers .
Verizon has the largest network and subscriber base , but does n't have any [ verizonwireless.com ] good smart phones .
[ wired.com ] T-mobile has the g1 , but T-mobile is [ etf-settlement.com ] a horrible [ cnet.com ] company .
AT&amp;T has the iphone but it costs a fortune [ att.com ] for service .
The key will be what smart phone takes hold on Verizon ; currently it looks like it is going to be an android phone .
Verizon Wireless : 87.7 Million subscribers [ wikipedia.org ] AT&amp;T Mobility : 79.6 Million Subscribers [ wikipedia.org ] Sprint : 49.3 Million subscribers [ wikipedia.org ] T-Mobile : 38.2 million subscribers [ wikipedia.org ] Personally I 'm waiting for a phone similar to the G1 to be available on the Verizon network .</tokentext>
<sentencetext>The key is the carriers.
Verizon has the largest network and subscriber base,

but doesn't have any  [verizonwireless.com]
good smart phones.
[wired.com] 
T-mobile has the g1, but T-mobile
is [etf-settlement.com]
a horrible [cnet.com] company.
AT&amp;T has the iphone but it
costs a fortune [att.com] for service.
The key will be what smart phone takes hold on Verizon; currently it looks like it is going to be an android phone.
Verizon Wireless: 87.7 Million subscribers [wikipedia.org] 
AT&amp;T Mobility: 79.6 Million Subscribers [wikipedia.org] 
Sprint: 49.3 Million subscribers [wikipedia.org] 
T-Mobile: 38.2 million subscribers [wikipedia.org] 

Personally I'm waiting for a phone similar to the G1 to be available on the Verizon network.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>Anonymous</author>
	<datestamp>1255525140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Twenty years ago, in Europe, the PC was a dull machine that you only ever ran business applications on. Maybe a flight simulator if you're lucky. The Mac was an obscure machine for desktop publishing. If you wanted gaming, you bought an Amiga or Atari ST. Now look where we are.</p><p>You're pointing at the entrenched PC games market, where everyone has hugely invested in writing in C++ for the Microsoft Direct3D API.</p><p>By comparison, smartphones are relatively new and the investment in Apple's iPhone API is tiny compared to the gigantic Windows-only ecosystem (Windows-only middleware, Windows-only tools, Windows-only 3D programmers, etc.) that keeps gaming chained to PCs.</p><p>So, given Android programming is much easier (far more programmers know Java than Objective C), and there's not <i>yet</i> a huge iPhone-only ecosystem in place, switching is still relatively painless. All it would take is one damn good phone running Android to topple Apple off its perch.</p></htmltext>
<tokenext>Twenty years ago , in Europe , the PC was a dull machine that you only ever ran business applications on .
Maybe a flight simulator if you 're lucky .
The Mac was an obscure machine for desktop publishing .
If you wanted gaming , you bought an Amiga or Atari ST. Now look where we are.You 're pointing at the entrenched PC games market , where everyone has hugely invested in writing in C + + for the Microsoft Direct3D API.By comparison , smartphones are relatively new and the investment in Apple 's iPhone API is tiny compared to the gigantic Windows-only ecosystem ( Windows-only middleware , Windows-only tools , Windows-only 3D programmers , etc .
) that keeps gaming chained to PCs.So , given Android programming is much easier ( far more programmers know Java than Objective C ) , and there 's not yet a huge iPhone-only ecosystem in place , switching is still relatively painless .
All it would take is one damn good phone running Android to topple Apple off its perch .</tokentext>
<sentencetext>Twenty years ago, in Europe, the PC was a dull machine that you only ever ran business applications on.
Maybe a flight simulator if you're lucky.
The Mac was an obscure machine for desktop publishing.
If you wanted gaming, you bought an Amiga or Atari ST. Now look where we are.You're pointing at the entrenched PC games market, where everyone has hugely invested in writing in C++ for the Microsoft Direct3D API.By comparison, smartphones are relatively new and the investment in Apple's iPhone API is tiny compared to the gigantic Windows-only ecosystem (Windows-only middleware, Windows-only tools, Windows-only 3D programmers, etc.
) that keeps gaming chained to PCs.So, given Android programming is much easier (far more programmers know Java than Objective C), and there's not yet a huge iPhone-only ecosystem in place, switching is still relatively painless.
All it would take is one damn good phone running Android to topple Apple off its perch.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744007</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>Anonymous</author>
	<datestamp>1255532100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>To take out the market of PS2 and PS3 (and pushing their platform-dependant Direct3D API onto that market as well).</p></htmltext>
<tokenext>To take out the market of PS2 and PS3 ( and pushing their platform-dependant Direct3D API onto that market as well ) .</tokentext>
<sentencetext>To take out the market of PS2 and PS3 (and pushing their platform-dependant Direct3D API onto that market as well).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29745215</id>
	<title>Programming language and game development</title>
	<author>UseCase</author>
	<datestamp>1255537140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If you are making your platform choice based solely on the primary development language of the platform then you might not be ready for game development. The knowledge and understanding necessary for making something as complicated as a video game transcends programming language.</htmltext>
<tokenext>If you are making your platform choice based solely on the primary development language of the platform then you might not be ready for game development .
The knowledge and understanding necessary for making something as complicated as a video game transcends programming language .</tokentext>
<sentencetext>If you are making your platform choice based solely on the primary development language of the platform then you might not be ready for game development.
The knowledge and understanding necessary for making something as complicated as a video game transcends programming language.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744077</id>
	<title>Re:Trendy</title>
	<author>RyuuzakiTetsuya</author>
	<datestamp>1255532460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Android phones are a usability mess.</p><p>I was out on a smoke break with a friend of mine who owns a G1 a few weeks ago.  I was also bashing out some mobile specific web app and wanted to test it with a G1.</p><p>Because the fact that<nobr> <wbr></nobr>/, -, and some other common symbols are hidden in weird places on the keyboard, it took me a bit to get to my own app, even on the soft keyboard.</p><p>I don't care what's under the hood, usability is king among consumers.  Freedom?  That's a huge after thought.</p></htmltext>
<tokenext>Android phones are a usability mess.I was out on a smoke break with a friend of mine who owns a G1 a few weeks ago .
I was also bashing out some mobile specific web app and wanted to test it with a G1.Because the fact that / , - , and some other common symbols are hidden in weird places on the keyboard , it took me a bit to get to my own app , even on the soft keyboard.I do n't care what 's under the hood , usability is king among consumers .
Freedom ? That 's a huge after thought .</tokentext>
<sentencetext>Android phones are a usability mess.I was out on a smoke break with a friend of mine who owns a G1 a few weeks ago.
I was also bashing out some mobile specific web app and wanted to test it with a G1.Because the fact that /, -, and some other common symbols are hidden in weird places on the keyboard, it took me a bit to get to my own app, even on the soft keyboard.I don't care what's under the hood, usability is king among consumers.
Freedom?  That's a huge after thought.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743799</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>SQLGuru</author>
	<datestamp>1255531080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Honestly, I think the only reason why the iPhone will be tough to beat (and FWIW, I have Windows Mobile and am considering Android) is iTunes.  iTunes is locked to Apple products and is a huge factor in what will make or break a platform.  If people can't get their music out of iTunes and on to their phone, the platform won't succeed.  If a "better iTunes" came along that wasn't tied to Apple products, you might see people flocking away from the vendor lock in.  The App store was initially a key differentiator, but all platforms are getting one (and I'm surprised it took MS this long since WinMo has been around this long).  And really, the killer app is still iTunes.</p></htmltext>
<tokenext>Honestly , I think the only reason why the iPhone will be tough to beat ( and FWIW , I have Windows Mobile and am considering Android ) is iTunes .
iTunes is locked to Apple products and is a huge factor in what will make or break a platform .
If people ca n't get their music out of iTunes and on to their phone , the platform wo n't succeed .
If a " better iTunes " came along that was n't tied to Apple products , you might see people flocking away from the vendor lock in .
The App store was initially a key differentiator , but all platforms are getting one ( and I 'm surprised it took MS this long since WinMo has been around this long ) .
And really , the killer app is still iTunes .</tokentext>
<sentencetext>Honestly, I think the only reason why the iPhone will be tough to beat (and FWIW, I have Windows Mobile and am considering Android) is iTunes.
iTunes is locked to Apple products and is a huge factor in what will make or break a platform.
If people can't get their music out of iTunes and on to their phone, the platform won't succeed.
If a "better iTunes" came along that wasn't tied to Apple products, you might see people flocking away from the vendor lock in.
The App store was initially a key differentiator, but all platforms are getting one (and I'm surprised it took MS this long since WinMo has been around this long).
And really, the killer app is still iTunes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743405</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>Anonymous</author>
	<datestamp>1255529040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>A good phone unlike my HTC Magic that randomly decided yesterday to start vibrating at its highest setting for no reason until I removed the battery?</htmltext>
<tokenext>A good phone unlike my HTC Magic that randomly decided yesterday to start vibrating at its highest setting for no reason until I removed the battery ?</tokentext>
<sentencetext>A good phone unlike my HTC Magic that randomly decided yesterday to start vibrating at its highest setting for no reason until I removed the battery?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743579</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>Zwergin</author>
	<datestamp>1255530060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I am looking forward to how the Android mobile devices look over the next year, and especially for those including NVidia's Tegra APX chip line.  They have been hyping it long enough as already integrated to work with the Android OS, I would hope some mobile device makers have jumped on board.
<br> <br>
     <a href="http://www.nvidia.com/object/product\_tegra\_apx\_us.html" title="nvidia.com" rel="nofollow">http://www.nvidia.com/object/product\_tegra\_apx\_us.html</a> [nvidia.com]
<br> <br>
~Zwergin</htmltext>
<tokenext>I am looking forward to how the Android mobile devices look over the next year , and especially for those including NVidia 's Tegra APX chip line .
They have been hyping it long enough as already integrated to work with the Android OS , I would hope some mobile device makers have jumped on board .
http : //www.nvidia.com/object/product \ _tegra \ _apx \ _us.html [ nvidia.com ] ~ Zwergin</tokentext>
<sentencetext>I am looking forward to how the Android mobile devices look over the next year, and especially for those including NVidia's Tegra APX chip line.
They have been hyping it long enough as already integrated to work with the Android OS, I would hope some mobile device makers have jumped on board.
http://www.nvidia.com/object/product\_tegra\_apx\_us.html [nvidia.com]
 
~Zwergin</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744163</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>vhogemann</author>
	<datestamp>1255532760000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Objective-C is not all that bad...</p><p>I'm a Java Web developer, without any real experience on desktop programming. But recently I was given the chance to do a small iPhone app for one of our clients, so I had to learn Objective-C from scratch to do it.</p><p>Objective-C might seem a little weird at first, but when you got used to the sintax the concepts used on the frameworks are not all that different from the Java counterparts. Appkit for example is much more pleasant to work with than Swing, for example.</p><p>It took around a week to learn the Objective-C basics, and another week to build a fairly complete prototype of the application.</p><p>So while might be a barrier for Java developers, it's not that high.</p></htmltext>
<tokenext>Objective-C is not all that bad...I 'm a Java Web developer , without any real experience on desktop programming .
But recently I was given the chance to do a small iPhone app for one of our clients , so I had to learn Objective-C from scratch to do it.Objective-C might seem a little weird at first , but when you got used to the sintax the concepts used on the frameworks are not all that different from the Java counterparts .
Appkit for example is much more pleasant to work with than Swing , for example.It took around a week to learn the Objective-C basics , and another week to build a fairly complete prototype of the application.So while might be a barrier for Java developers , it 's not that high .</tokentext>
<sentencetext>Objective-C is not all that bad...I'm a Java Web developer, without any real experience on desktop programming.
But recently I was given the chance to do a small iPhone app for one of our clients, so I had to learn Objective-C from scratch to do it.Objective-C might seem a little weird at first, but when you got used to the sintax the concepts used on the frameworks are not all that different from the Java counterparts.
Appkit for example is much more pleasant to work with than Swing, for example.It took around a week to learn the Objective-C basics, and another week to build a fairly complete prototype of the application.So while might be a barrier for Java developers, it's not that high.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743229</id>
	<title>Re:Trendy</title>
	<author>Rakshasa Taisab</author>
	<datestamp>1255527780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yeah, cause everyone out there is just waiting for a chance to stick it to the man (or fruit) and rid themselves of the chains of tyranny.<br> <br>

Using, and developing for, an iPod touch (can't afford the iPhone) I fail to see how my hands are 'tied' or how a regular user would ever 'realize their hands are tied'. Dream on Mr. Revolutionary Geek, and make sure you fight the power of sleek designs.</htmltext>
<tokenext>Yeah , cause everyone out there is just waiting for a chance to stick it to the man ( or fruit ) and rid themselves of the chains of tyranny .
Using , and developing for , an iPod touch ( ca n't afford the iPhone ) I fail to see how my hands are 'tied ' or how a regular user would ever 'realize their hands are tied' .
Dream on Mr. Revolutionary Geek , and make sure you fight the power of sleek designs .</tokentext>
<sentencetext>Yeah, cause everyone out there is just waiting for a chance to stick it to the man (or fruit) and rid themselves of the chains of tyranny.
Using, and developing for, an iPod touch (can't afford the iPhone) I fail to see how my hands are 'tied' or how a regular user would ever 'realize their hands are tied'.
Dream on Mr. Revolutionary Geek, and make sure you fight the power of sleek designs.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743369</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>Mjlner</author>
	<datestamp>1255528740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The way the section quoted in the summary plays up the "wide-open field" of Android just strikes me as very silly. If you replaced "Android" with "Mac" and "iPhone" with "Windows," you'd have a pretty good approximation of the marketshare situation in the PC game market...and no one's suggesting that writing games for Mac is smarter than writing games for Windows due to massive overcrowding of the Windows games market.</p></div><p>...and no one's suggesting that writing games for the iPhone is dumber, because the market is overcrowded. The quoted section is saying that there's more competition and the competition is strong, whereas the payoff - if you succeed - is huge... which is also true for the Windows game market, of course.</p></div>
	</htmltext>
<tokenext>The way the section quoted in the summary plays up the " wide-open field " of Android just strikes me as very silly .
If you replaced " Android " with " Mac " and " iPhone " with " Windows , " you 'd have a pretty good approximation of the marketshare situation in the PC game market...and no one 's suggesting that writing games for Mac is smarter than writing games for Windows due to massive overcrowding of the Windows games market....and no one 's suggesting that writing games for the iPhone is dumber , because the market is overcrowded .
The quoted section is saying that there 's more competition and the competition is strong , whereas the payoff - if you succeed - is huge... which is also true for the Windows game market , of course .</tokentext>
<sentencetext>The way the section quoted in the summary plays up the "wide-open field" of Android just strikes me as very silly.
If you replaced "Android" with "Mac" and "iPhone" with "Windows," you'd have a pretty good approximation of the marketshare situation in the PC game market...and no one's suggesting that writing games for Mac is smarter than writing games for Windows due to massive overcrowding of the Windows games market....and no one's suggesting that writing games for the iPhone is dumber, because the market is overcrowded.
The quoted section is saying that there's more competition and the competition is strong, whereas the payoff - if you succeed - is huge... which is also true for the Windows game market, of course.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744251</id>
	<title>Re:opinion</title>
	<author>mdwh2</author>
	<datestamp>1255533180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Personally I'd rather not return to the bad old days where every phone was incompatible with each other, but:</p><p><i>Apple has the advantage of controlling both the platform and the device. So you know that whatever you develop for the iPhone it will work.</i></p><p>There's nothing stopping you from developing for one specific brand of phones. Indeed, this is precisely why such a comparison is ludicrous - and what about all the other phones out there? Even if you stick to one brand, there are plenty of others, that sell more than Apple (e.g., Nokia, Blackberry).</p></htmltext>
<tokenext>Personally I 'd rather not return to the bad old days where every phone was incompatible with each other , but : Apple has the advantage of controlling both the platform and the device .
So you know that whatever you develop for the iPhone it will work.There 's nothing stopping you from developing for one specific brand of phones .
Indeed , this is precisely why such a comparison is ludicrous - and what about all the other phones out there ?
Even if you stick to one brand , there are plenty of others , that sell more than Apple ( e.g. , Nokia , Blackberry ) .</tokentext>
<sentencetext>Personally I'd rather not return to the bad old days where every phone was incompatible with each other, but:Apple has the advantage of controlling both the platform and the device.
So you know that whatever you develop for the iPhone it will work.There's nothing stopping you from developing for one specific brand of phones.
Indeed, this is precisely why such a comparison is ludicrous - and what about all the other phones out there?
Even if you stick to one brand, there are plenty of others, that sell more than Apple (e.g., Nokia, Blackberry).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744159</id>
	<title>Got my HTC HERO w/Android yesterday</title>
	<author>bmwEnthusiast</author>
	<datestamp>1255532760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I am in love with my new phone. The Android Marketplace from what I can tell is almost \%80 free. I plan to personally download the SDK and Eclipse stuff and make my own apps/games in java.

The Hero is a solidly built phone with every feature you could ask for including exchange sync.

Love it!</htmltext>
<tokenext>I am in love with my new phone .
The Android Marketplace from what I can tell is almost \ % 80 free .
I plan to personally download the SDK and Eclipse stuff and make my own apps/games in java .
The Hero is a solidly built phone with every feature you could ask for including exchange sync .
Love it !</tokentext>
<sentencetext>I am in love with my new phone.
The Android Marketplace from what I can tell is almost \%80 free.
I plan to personally download the SDK and Eclipse stuff and make my own apps/games in java.
The Hero is a solidly built phone with every feature you could ask for including exchange sync.
Love it!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742911</id>
	<title>Tempting</title>
	<author>Canazza</author>
	<datestamp>1255524360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Android is definitly a tempting choice for development - purely because of the ease in which you can push a product to market. But then again, there's also Symbian, which is used on things like the Nokia N97, which has been around for ages (in various itterations), the latest one is the true smart-phone style thing, but I have a 3 year old phone with an older version of Symbian on it that can still run Java Games, meaning there is already the possibility of a large market for simple apps that can run on older phones as well as the newer smartphones</p></htmltext>
<tokenext>Android is definitly a tempting choice for development - purely because of the ease in which you can push a product to market .
But then again , there 's also Symbian , which is used on things like the Nokia N97 , which has been around for ages ( in various itterations ) , the latest one is the true smart-phone style thing , but I have a 3 year old phone with an older version of Symbian on it that can still run Java Games , meaning there is already the possibility of a large market for simple apps that can run on older phones as well as the newer smartphones</tokentext>
<sentencetext>Android is definitly a tempting choice for development - purely because of the ease in which you can push a product to market.
But then again, there's also Symbian, which is used on things like the Nokia N97, which has been around for ages (in various itterations), the latest one is the true smart-phone style thing, but I have a 3 year old phone with an older version of Symbian on it that can still run Java Games, meaning there is already the possibility of a large market for simple apps that can run on older phones as well as the newer smartphones</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29753603</id>
	<title>Seriously?</title>
	<author>Anonymous</author>
	<datestamp>1255544460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"relatively more programmer-friendly Java" -- LOL!</p></htmltext>
<tokenext>" relatively more programmer-friendly Java " -- LOL !</tokentext>
<sentencetext>"relatively more programmer-friendly Java" -- LOL!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742925</id>
	<title>Re:opinion</title>
	<author>Nerdfest</author>
	<datestamp>1255524420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Of course, your game console has a proper controller.</htmltext>
<tokenext>Of course , your game console has a proper controller .</tokentext>
<sentencetext>Of course, your game console has a proper controller.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746313</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>GreyWolf3000</author>
	<datestamp>1255541520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"So, given Android programming is much easier (far more programmers know Java than Objective C)"</p><p>Yeah, and Windows is easier than Linux because for more people use it.</p></htmltext>
<tokenext>" So , given Android programming is much easier ( far more programmers know Java than Objective C ) " Yeah , and Windows is easier than Linux because for more people use it .</tokentext>
<sentencetext>"So, given Android programming is much easier (far more programmers know Java than Objective C)"Yeah, and Windows is easier than Linux because for more people use it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29745895</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>brkello</author>
	<datestamp>1255539840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Android will be difficult because it is so open.  It is on different devices with different capabilities and people can be all running their own custom OS.  This is a limitation for WinMo as well.  It isn't one for the iPhone and that is why it has taken off.</htmltext>
<tokenext>Android will be difficult because it is so open .
It is on different devices with different capabilities and people can be all running their own custom OS .
This is a limitation for WinMo as well .
It is n't one for the iPhone and that is why it has taken off .</tokentext>
<sentencetext>Android will be difficult because it is so open.
It is on different devices with different capabilities and people can be all running their own custom OS.
This is a limitation for WinMo as well.
It isn't one for the iPhone and that is why it has taken off.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29748823</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>ivucica</author>
	<datestamp>1255552560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Don't forget you can do much, much work with C++ and OpenGL. ObjC can be a tiny wrapper and OpenGL ES is very very similar to OpenGL (no glBegin()/glEnd() and added fixed-point fractional numbers, that's all I care about, really).</htmltext>
<tokenext>Do n't forget you can do much , much work with C + + and OpenGL .
ObjC can be a tiny wrapper and OpenGL ES is very very similar to OpenGL ( no glBegin ( ) /glEnd ( ) and added fixed-point fractional numbers , that 's all I care about , really ) .</tokentext>
<sentencetext>Don't forget you can do much, much work with C++ and OpenGL.
ObjC can be a tiny wrapper and OpenGL ES is very very similar to OpenGL (no glBegin()/glEnd() and added fixed-point fractional numbers, that's all I care about, really).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744509</id>
	<title>Friendly is in the libraries...</title>
	<author>SuperKendall</author>
	<datestamp>1255534260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Java vs. Objective-C is a non-starter compared to what libraries are available to each platform.</p><p>Most serious game developers on the iPhone aren't even writing much Objective-C - they often use a framework like Unity, which lets you script in Javascript or C#.</p><p>Even those using some of the free frameworks like Cocos2D are spending more time thinking about Cocos objects than they are about Objective-C syntax, which is pretty easy to pick up.  Syntax is only a tiny part of any modern platform, it's all about libraries... and even for application development the iPhone has a richer set of libraries than does Android (though Android is pretty close).</p></htmltext>
<tokenext>Java vs. Objective-C is a non-starter compared to what libraries are available to each platform.Most serious game developers on the iPhone are n't even writing much Objective-C - they often use a framework like Unity , which lets you script in Javascript or C # .Even those using some of the free frameworks like Cocos2D are spending more time thinking about Cocos objects than they are about Objective-C syntax , which is pretty easy to pick up .
Syntax is only a tiny part of any modern platform , it 's all about libraries... and even for application development the iPhone has a richer set of libraries than does Android ( though Android is pretty close ) .</tokentext>
<sentencetext>Java vs. Objective-C is a non-starter compared to what libraries are available to each platform.Most serious game developers on the iPhone aren't even writing much Objective-C - they often use a framework like Unity, which lets you script in Javascript or C#.Even those using some of the free frameworks like Cocos2D are spending more time thinking about Cocos objects than they are about Objective-C syntax, which is pretty easy to pick up.
Syntax is only a tiny part of any modern platform, it's all about libraries... and even for application development the iPhone has a richer set of libraries than does Android (though Android is pretty close).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742895</id>
	<title>hmmmm</title>
	<author>Anonymous</author>
	<datestamp>1255524240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Hmmm. Long-term investment with the potential for steady, but solid growth? Or the ridiculously slim chance of striking it big in an oversaturated market? As an American, I think I know which way my fellow countrymen will tend to lean.</htmltext>
<tokenext>Hmmm .
Long-term investment with the potential for steady , but solid growth ?
Or the ridiculously slim chance of striking it big in an oversaturated market ?
As an American , I think I know which way my fellow countrymen will tend to lean .</tokentext>
<sentencetext>Hmmm.
Long-term investment with the potential for steady, but solid growth?
Or the ridiculously slim chance of striking it big in an oversaturated market?
As an American, I think I know which way my fellow countrymen will tend to lean.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744369</id>
	<title>Has the RDF completely distorted your view?</title>
	<author>mdwh2</author>
	<datestamp>1255533660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Are you serious?</p><p>The Iphone may have a better market share than Android, but this isn't Windows to Mac, it's more like Mac to Linux, or I dunno, AmigaOS to RISC OS.</p><p>There are a vast range of companies in the phone market - none of them have a Windows like share, but for the larger companies, look at someone like Nokia.</p><p>I'm astonished at the sheer ignorance of the reality of the mobile market here - that people continue to propagate this myth that Apple are not only in the lead, but have a monopoly, when neither is true. Slashdot was once a place to come where people knew about the tech industry - sadly not anymore.</p></htmltext>
<tokenext>Are you serious ? The Iphone may have a better market share than Android , but this is n't Windows to Mac , it 's more like Mac to Linux , or I dunno , AmigaOS to RISC OS.There are a vast range of companies in the phone market - none of them have a Windows like share , but for the larger companies , look at someone like Nokia.I 'm astonished at the sheer ignorance of the reality of the mobile market here - that people continue to propagate this myth that Apple are not only in the lead , but have a monopoly , when neither is true .
Slashdot was once a place to come where people knew about the tech industry - sadly not anymore .</tokentext>
<sentencetext>Are you serious?The Iphone may have a better market share than Android, but this isn't Windows to Mac, it's more like Mac to Linux, or I dunno, AmigaOS to RISC OS.There are a vast range of companies in the phone market - none of them have a Windows like share, but for the larger companies, look at someone like Nokia.I'm astonished at the sheer ignorance of the reality of the mobile market here - that people continue to propagate this myth that Apple are not only in the lead, but have a monopoly, when neither is true.
Slashdot was once a place to come where people knew about the tech industry - sadly not anymore.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742885</id>
	<title>Objective C  Java</title>
	<author>Anonymous</author>
	<datestamp>1255524120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>&gt;in Objective C [...] more programmer-friendly Java.</p><p>[Arguments needed]</p></htmltext>
<tokenext>&gt; in Objective C [ ... ] more programmer-friendly Java .
[ Arguments needed ]</tokentext>
<sentencetext>&gt;in Objective C [...] more programmer-friendly Java.
[Arguments needed]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742875</id>
	<title>Re:opinion</title>
	<author>sopssa</author>
	<datestamp>1255524060000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>It's not really a problem in PC, it can be assumed everyone has atleast keyboard and a mouse and if you're playing games, graphics card too. What it comes down to is if you have enough RAM, CPU and powerful enough graphics card and you can see the requirements from the package (or online).</p><p>Phones are different because of the actual hardware differences. Like you said, some phones might have (multi)touch or not, physical keyboard or just software keyboard, 3d acceleration, different types of physical keyboards, different resolutions and so on. Since iPhone is always the same kind, it's easier to develop to it.</p><p>However for Windows Mobile and Symbian game developers have usually released different versions for different devices. It might create more barrier for an indie developer to entry the market because they have to test their software on all the supported devices and make adjustments, but for studios it's not so much work. But then again, big studios port their games to all platforms; Symbian, WM, iPhone and Android.</p><p>But Java on Android.. meh.</p></htmltext>
<tokenext>It 's not really a problem in PC , it can be assumed everyone has atleast keyboard and a mouse and if you 're playing games , graphics card too .
What it comes down to is if you have enough RAM , CPU and powerful enough graphics card and you can see the requirements from the package ( or online ) .Phones are different because of the actual hardware differences .
Like you said , some phones might have ( multi ) touch or not , physical keyboard or just software keyboard , 3d acceleration , different types of physical keyboards , different resolutions and so on .
Since iPhone is always the same kind , it 's easier to develop to it.However for Windows Mobile and Symbian game developers have usually released different versions for different devices .
It might create more barrier for an indie developer to entry the market because they have to test their software on all the supported devices and make adjustments , but for studios it 's not so much work .
But then again , big studios port their games to all platforms ; Symbian , WM , iPhone and Android.But Java on Android.. meh .</tokentext>
<sentencetext>It's not really a problem in PC, it can be assumed everyone has atleast keyboard and a mouse and if you're playing games, graphics card too.
What it comes down to is if you have enough RAM, CPU and powerful enough graphics card and you can see the requirements from the package (or online).Phones are different because of the actual hardware differences.
Like you said, some phones might have (multi)touch or not, physical keyboard or just software keyboard, 3d acceleration, different types of physical keyboards, different resolutions and so on.
Since iPhone is always the same kind, it's easier to develop to it.However for Windows Mobile and Symbian game developers have usually released different versions for different devices.
It might create more barrier for an indie developer to entry the market because they have to test their software on all the supported devices and make adjustments, but for studios it's not so much work.
But then again, big studios port their games to all platforms; Symbian, WM, iPhone and Android.But Java on Android.. meh.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744551</id>
	<title>iPhone supports C++ just fine</title>
	<author>drerwk</author>
	<datestamp>1255534440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I wrote the iPhone version of Repton primarily in C++. It is easy to mix Obj-C and C++, and I prefer C++ for OpenGL usage. A few UI items I implemented using the Cocoa Obj-C interfaces because Interface Builder is so pleasant to use.<br>Any one suggesting iPhone development is limited to Obj-C is inexperience in iPhone development. Any one suggesting Obj-C is hard to use compared to Java may have a point, but primarily because the Java IDEs are so good compared to XCode. As far a game dev goes, I prefer C++ to Java especially the OpenGL bindings, and  I think game dev benefits from new/delete control one has in C++.</htmltext>
<tokenext>I wrote the iPhone version of Repton primarily in C + + .
It is easy to mix Obj-C and C + + , and I prefer C + + for OpenGL usage .
A few UI items I implemented using the Cocoa Obj-C interfaces because Interface Builder is so pleasant to use.Any one suggesting iPhone development is limited to Obj-C is inexperience in iPhone development .
Any one suggesting Obj-C is hard to use compared to Java may have a point , but primarily because the Java IDEs are so good compared to XCode .
As far a game dev goes , I prefer C + + to Java especially the OpenGL bindings , and I think game dev benefits from new/delete control one has in C + + .</tokentext>
<sentencetext>I wrote the iPhone version of Repton primarily in C++.
It is easy to mix Obj-C and C++, and I prefer C++ for OpenGL usage.
A few UI items I implemented using the Cocoa Obj-C interfaces because Interface Builder is so pleasant to use.Any one suggesting iPhone development is limited to Obj-C is inexperience in iPhone development.
Any one suggesting Obj-C is hard to use compared to Java may have a point, but primarily because the Java IDEs are so good compared to XCode.
As far a game dev goes, I prefer C++ to Java especially the OpenGL bindings, and  I think game dev benefits from new/delete control one has in C++.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743341</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>craagz</author>
	<datestamp>1255528560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Reading this popped a question into my mind. <br> <br> With all this PC entrenchment, why did Microsoft launch Xbox? <br> <br>Someone explain, Please.</htmltext>
<tokenext>Reading this popped a question into my mind .
With all this PC entrenchment , why did Microsoft launch Xbox ?
Someone explain , Please .</tokentext>
<sentencetext>Reading this popped a question into my mind.
With all this PC entrenchment, why did Microsoft launch Xbox?
Someone explain, Please.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29753705</id>
	<title>Re:The stats say it all</title>
	<author>MemoryDragon</author>
	<datestamp>1255545660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually Android is not as bad as J2ME the main problem with J2ME was simply you had a very small API and almost no support for extended feates, heck even only a handful of UI input fields.<br>Android is way more extensive and a full os instead of a vm with a dozend or so apis (the important ones always came from the vendors)<br>So far the Android mobiles perform quite nicely regarding compatibility, all programs so far run on all android mobiles unmodified.<br>Just because the underlying language in both systems is java does not mean that both systems are comparable, Java is after all just a language nothing more.</p></htmltext>
<tokenext>Actually Android is not as bad as J2ME the main problem with J2ME was simply you had a very small API and almost no support for extended feates , heck even only a handful of UI input fields.Android is way more extensive and a full os instead of a vm with a dozend or so apis ( the important ones always came from the vendors ) So far the Android mobiles perform quite nicely regarding compatibility , all programs so far run on all android mobiles unmodified.Just because the underlying language in both systems is java does not mean that both systems are comparable , Java is after all just a language nothing more .</tokentext>
<sentencetext>Actually Android is not as bad as J2ME the main problem with J2ME was simply you had a very small API and almost no support for extended feates, heck even only a handful of UI input fields.Android is way more extensive and a full os instead of a vm with a dozend or so apis (the important ones always came from the vendors)So far the Android mobiles perform quite nicely regarding compatibility, all programs so far run on all android mobiles unmodified.Just because the underlying language in both systems is java does not mean that both systems are comparable, Java is after all just a language nothing more.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746301</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743389</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>Anonymous</author>
	<datestamp>1255528860000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext>Not everything changes.  In Europe the Mac is still an obscure machine for desktop publishing.</htmltext>
<tokenext>Not everything changes .
In Europe the Mac is still an obscure machine for desktop publishing .</tokentext>
<sentencetext>Not everything changes.
In Europe the Mac is still an obscure machine for desktop publishing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746223</id>
	<title>Wow....</title>
	<author>sbeckstead</author>
	<datestamp>1255541160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>but the possibility of potential growth</i> <br>
Don't step in all that potential.</htmltext>
<tokenext>but the possibility of potential growth Do n't step in all that potential .</tokentext>
<sentencetext>but the possibility of potential growth 
Don't step in all that potential.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746301</id>
	<title>The stats say it all</title>
	<author>Lysol</author>
	<datestamp>1255541460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>While 90k+ apps &amp; over 2bln downloads makes it harder to get noticed, those numbers say it all.</p><p>I've used a few Android phones and I like them. But the thing that makes the iPhone great to develop for (after you get past obj-c hurdle, the api's are actually really good) is that it's *standard*. One form factor, end of story. I can't help but think Android is gonna fall into the same hole that J2ME did when it tried to support everything. Already developers are maintaining separate branches for separate devices for Android. I've developed J2ME apps before and they are a f-ing nightmare. That platform never took off for a reason, because there's *too much* choice and diversity. Everything to all people; good luck.</p><p>There are also no where near as many Android users as iPhone and so developing for that platform with the intent to make some money on your app is not very plausible at this point. Maybe in a few years, maybe not. (Plus I hate Eclipse, so much unnecessary bloat, just like Java. I want tools that are fast and that don't require 5mil downloads of some frameworks I'll never use. But the Eclipse thing is only my hang up and I'm sure most Android devs won't care.)</p><p>So as a developer what makes more sense? 5 code bases for 5 Android phones - all with different form factors / features - and relatively little money for all your toil? Or one platform and the chance to hit it big? It's the same argument on a PC; develop for the huge Windows market, or everyone else?</p></htmltext>
<tokenext>While 90k + apps &amp; over 2bln downloads makes it harder to get noticed , those numbers say it all.I 've used a few Android phones and I like them .
But the thing that makes the iPhone great to develop for ( after you get past obj-c hurdle , the api 's are actually really good ) is that it 's * standard * .
One form factor , end of story .
I ca n't help but think Android is gon na fall into the same hole that J2ME did when it tried to support everything .
Already developers are maintaining separate branches for separate devices for Android .
I 've developed J2ME apps before and they are a f-ing nightmare .
That platform never took off for a reason , because there 's * too much * choice and diversity .
Everything to all people ; good luck.There are also no where near as many Android users as iPhone and so developing for that platform with the intent to make some money on your app is not very plausible at this point .
Maybe in a few years , maybe not .
( Plus I hate Eclipse , so much unnecessary bloat , just like Java .
I want tools that are fast and that do n't require 5mil downloads of some frameworks I 'll never use .
But the Eclipse thing is only my hang up and I 'm sure most Android devs wo n't care .
) So as a developer what makes more sense ?
5 code bases for 5 Android phones - all with different form factors / features - and relatively little money for all your toil ?
Or one platform and the chance to hit it big ?
It 's the same argument on a PC ; develop for the huge Windows market , or everyone else ?</tokentext>
<sentencetext>While 90k+ apps &amp; over 2bln downloads makes it harder to get noticed, those numbers say it all.I've used a few Android phones and I like them.
But the thing that makes the iPhone great to develop for (after you get past obj-c hurdle, the api's are actually really good) is that it's *standard*.
One form factor, end of story.
I can't help but think Android is gonna fall into the same hole that J2ME did when it tried to support everything.
Already developers are maintaining separate branches for separate devices for Android.
I've developed J2ME apps before and they are a f-ing nightmare.
That platform never took off for a reason, because there's *too much* choice and diversity.
Everything to all people; good luck.There are also no where near as many Android users as iPhone and so developing for that platform with the intent to make some money on your app is not very plausible at this point.
Maybe in a few years, maybe not.
(Plus I hate Eclipse, so much unnecessary bloat, just like Java.
I want tools that are fast and that don't require 5mil downloads of some frameworks I'll never use.
But the Eclipse thing is only my hang up and I'm sure most Android devs won't care.
)So as a developer what makes more sense?
5 code bases for 5 Android phones - all with different form factors / features - and relatively little money for all your toil?
Or one platform and the chance to hit it big?
It's the same argument on a PC; develop for the huge Windows market, or everyone else?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847</id>
	<title>Seems a trifle disingenuous to me</title>
	<author>danaris</author>
	<datestamp>1255523580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>The way the section quoted in the summary plays up the "wide-open field" of Android just strikes me as very silly. If you replaced "Android" with "Mac" and "iPhone" with "Windows," you'd have a pretty good approximation of the marketshare situation in the PC game market...and no one's suggesting that writing games for Mac is smarter than writing games for Windows due to massive overcrowding of the Windows games market.</p><p> <i>(Apologies for any incoherence. Please blame posting before fully waking up.)</i> </p><p>Dan Aris</p></htmltext>
<tokenext>The way the section quoted in the summary plays up the " wide-open field " of Android just strikes me as very silly .
If you replaced " Android " with " Mac " and " iPhone " with " Windows , " you 'd have a pretty good approximation of the marketshare situation in the PC game market...and no one 's suggesting that writing games for Mac is smarter than writing games for Windows due to massive overcrowding of the Windows games market .
( Apologies for any incoherence .
Please blame posting before fully waking up .
) Dan Aris</tokentext>
<sentencetext>The way the section quoted in the summary plays up the "wide-open field" of Android just strikes me as very silly.
If you replaced "Android" with "Mac" and "iPhone" with "Windows," you'd have a pretty good approximation of the marketshare situation in the PC game market...and no one's suggesting that writing games for Mac is smarter than writing games for Windows due to massive overcrowding of the Windows games market.
(Apologies for any incoherence.
Please blame posting before fully waking up.
) Dan Aris</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744015</id>
	<title>Re:opinion</title>
	<author>Wallslide</author>
	<datestamp>1255532100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>In that case, which is the better comparison (with respect to games of course): the difference between PCs and consoles or the difference between Apple computers and the Windows PC ecosystem?  <br>
If we compare the iPhone vs. Android situation to PCs versus consoles, then we have an Enthusiast market versus a casual market (where basically different game types work better on either a PC or a console).  If we instead make the comparison to Apple versus the PC market, then Apple pretty much lost in that respect, and eventually the iPhone should lose out to the avalanche of rapidly evolving Android devices.</htmltext>
<tokenext>In that case , which is the better comparison ( with respect to games of course ) : the difference between PCs and consoles or the difference between Apple computers and the Windows PC ecosystem ?
If we compare the iPhone vs. Android situation to PCs versus consoles , then we have an Enthusiast market versus a casual market ( where basically different game types work better on either a PC or a console ) .
If we instead make the comparison to Apple versus the PC market , then Apple pretty much lost in that respect , and eventually the iPhone should lose out to the avalanche of rapidly evolving Android devices .</tokentext>
<sentencetext>In that case, which is the better comparison (with respect to games of course): the difference between PCs and consoles or the difference between Apple computers and the Windows PC ecosystem?
If we compare the iPhone vs. Android situation to PCs versus consoles, then we have an Enthusiast market versus a casual market (where basically different game types work better on either a PC or a console).
If we instead make the comparison to Apple versus the PC market, then Apple pretty much lost in that respect, and eventually the iPhone should lose out to the avalanche of rapidly evolving Android devices.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29745519</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>pjt33</author>
	<datestamp>1255538400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I don't recall seeing any commercial games written in Java ever.</p></div><p>Have you never heard of browser games? Mobile phone games? There are thousands of commercial Java games, and some of them have made profits in the hundreds of millions.</p></div>
	</htmltext>
<tokenext>I do n't recall seeing any commercial games written in Java ever.Have you never heard of browser games ?
Mobile phone games ?
There are thousands of commercial Java games , and some of them have made profits in the hundreds of millions .</tokentext>
<sentencetext>I don't recall seeing any commercial games written in Java ever.Have you never heard of browser games?
Mobile phone games?
There are thousands of commercial Java games, and some of them have made profits in the hundreds of millions.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744515</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29751815</id>
	<title>Re:opinion</title>
	<author>zonker</author>
	<datestamp>1255526760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>That's probably true.  Unfortunately most people I know that have an Android phone like the OS but hate the hardware (mostly the G1).  Being IT people and a rather vocal group they tend to advise others as far as purchases go.  The early Android phones are still lacking, especially in battery life which games will eat up like there is no tomorrow.</p></htmltext>
<tokenext>That 's probably true .
Unfortunately most people I know that have an Android phone like the OS but hate the hardware ( mostly the G1 ) .
Being IT people and a rather vocal group they tend to advise others as far as purchases go .
The early Android phones are still lacking , especially in battery life which games will eat up like there is no tomorrow .</tokentext>
<sentencetext>That's probably true.
Unfortunately most people I know that have an Android phone like the OS but hate the hardware (mostly the G1).
Being IT people and a rather vocal group they tend to advise others as far as purchases go.
The early Android phones are still lacking, especially in battery life which games will eat up like there is no tomorrow.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743527</id>
	<title>Quality control</title>
	<author>moankey</author>
	<datestamp>1255529760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have to agree to a certain level. Apple has a level of quality control that people tend to forget and think of it more as a proprietary system. Its true Apple does not make sense in their choices most of the time and for some reason it works. A elite cliche type of expression if you own their products.</p><p>Whiles others that see room for improvement in their model try the same with looser controls and it never seems to be able to catch that distortion field momentum that Jobs is so good at creating.</p></htmltext>
<tokenext>I have to agree to a certain level .
Apple has a level of quality control that people tend to forget and think of it more as a proprietary system .
Its true Apple does not make sense in their choices most of the time and for some reason it works .
A elite cliche type of expression if you own their products.Whiles others that see room for improvement in their model try the same with looser controls and it never seems to be able to catch that distortion field momentum that Jobs is so good at creating .</tokentext>
<sentencetext>I have to agree to a certain level.
Apple has a level of quality control that people tend to forget and think of it more as a proprietary system.
Its true Apple does not make sense in their choices most of the time and for some reason it works.
A elite cliche type of expression if you own their products.Whiles others that see room for improvement in their model try the same with looser controls and it never seems to be able to catch that distortion field momentum that Jobs is so good at creating.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744145</id>
	<title>Re:opinion</title>
	<author>amoeba1911</author>
	<datestamp>1255532700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I completely agree, Apple has the advantage of having all of their hardware being the same, makes development easier, and users don't have to worry about different requirements. Other platforms like Android or Windows forces you <b>think different</b>, not a familiar concept in Apple land despite the fact that it's their main slogan.</htmltext>
<tokenext>I completely agree , Apple has the advantage of having all of their hardware being the same , makes development easier , and users do n't have to worry about different requirements .
Other platforms like Android or Windows forces you think different , not a familiar concept in Apple land despite the fact that it 's their main slogan .</tokentext>
<sentencetext>I completely agree, Apple has the advantage of having all of their hardware being the same, makes development easier, and users don't have to worry about different requirements.
Other platforms like Android or Windows forces you think different, not a familiar concept in Apple land despite the fact that it's their main slogan.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744121</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>WaywardGeek</author>
	<datestamp>1255532640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>All it would take is one damn good phone running Android to topple Apple off its perch.</p></div></blockquote><p>This is absolutely key, and for some reason, stupid cell-phone marketing guys don't get it.  <a href="http://www.theregister.co.uk/2008/04/09/cat\_keynes\_motorola/" title="theregister.co.uk">Motorola should recall how the RAZR happened</a> [theregister.co.uk].  In short, a brilliant marketing guy at Motorola with the clout to ignore everyone else forced Motorola to build the RAZR.<br>It turns out that every time a marketing department is allowed to design the next product, they do user forums and talk to the sales team.  The one thing that comes back loud and clear is "Make it cheaper!".  Thus, we get crap like the new Motorola CLIQ.<br>It takes a genius like Steve Jobs to understand why we actually want products that are over-priced and beautiful, even when they offer no new functionality: we're stupid and vain.  When asked, we all say, "all I care about is functionality... I'm not vain!"  Then, at the store, our true nature takes over and we fork over $$ for the pretty objects.<br>Why can't marketing guys figure this out?<br>And... I <i>am</i> vain.  I've owned an iPhone and currently own a T-Mobile G1.  My G1 has some real problems - the camera sucks, the battery is wimpy, it has no built-in flash, it's bigger than an iPhone but has a smaller screen... however, what really pisses me off about it is that it's ugly and clunky!  Make a beautiful Android phone, and I will switch carriers, fork over $400, and sign a two year contract!<br>Marketing morons: I'm your typical user!</p></div>
	</htmltext>
<tokenext>All it would take is one damn good phone running Android to topple Apple off its perch.This is absolutely key , and for some reason , stupid cell-phone marketing guys do n't get it .
Motorola should recall how the RAZR happened [ theregister.co.uk ] .
In short , a brilliant marketing guy at Motorola with the clout to ignore everyone else forced Motorola to build the RAZR.It turns out that every time a marketing department is allowed to design the next product , they do user forums and talk to the sales team .
The one thing that comes back loud and clear is " Make it cheaper ! " .
Thus , we get crap like the new Motorola CLIQ.It takes a genius like Steve Jobs to understand why we actually want products that are over-priced and beautiful , even when they offer no new functionality : we 're stupid and vain .
When asked , we all say , " all I care about is functionality... I 'm not vain !
" Then , at the store , our true nature takes over and we fork over $ $ for the pretty objects.Why ca n't marketing guys figure this out ? And... I am vain .
I 've owned an iPhone and currently own a T-Mobile G1 .
My G1 has some real problems - the camera sucks , the battery is wimpy , it has no built-in flash , it 's bigger than an iPhone but has a smaller screen... however , what really pisses me off about it is that it 's ugly and clunky !
Make a beautiful Android phone , and I will switch carriers , fork over $ 400 , and sign a two year contract ! Marketing morons : I 'm your typical user !</tokentext>
<sentencetext>All it would take is one damn good phone running Android to topple Apple off its perch.This is absolutely key, and for some reason, stupid cell-phone marketing guys don't get it.
Motorola should recall how the RAZR happened [theregister.co.uk].
In short, a brilliant marketing guy at Motorola with the clout to ignore everyone else forced Motorola to build the RAZR.It turns out that every time a marketing department is allowed to design the next product, they do user forums and talk to the sales team.
The one thing that comes back loud and clear is "Make it cheaper!".
Thus, we get crap like the new Motorola CLIQ.It takes a genius like Steve Jobs to understand why we actually want products that are over-priced and beautiful, even when they offer no new functionality: we're stupid and vain.
When asked, we all say, "all I care about is functionality... I'm not vain!
"  Then, at the store, our true nature takes over and we fork over $$ for the pretty objects.Why can't marketing guys figure this out?And... I am vain.
I've owned an iPhone and currently own a T-Mobile G1.
My G1 has some real problems - the camera sucks, the battery is wimpy, it has no built-in flash, it's bigger than an iPhone but has a smaller screen... however, what really pisses me off about it is that it's ugly and clunky!
Make a beautiful Android phone, and I will switch carriers, fork over $400, and sign a two year contract!Marketing morons: I'm your typical user!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744515</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>foniksonik</author>
	<datestamp>1255534260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How many game developers know Java? General purpose developers don't count... sure they could make a simple logic game and add fancy graphics on top but something like Super Monkey Ball?</p><p>I don't recall seeing any commercial games written in Java ever. In this scenario, why would a game developer choose to write games in a language completely different from C++ when there is Obj-C which has the similarity right there in the name.. sure it's not C++ but that doesn't seemed to have stopped ALL of the major game dev companies from releasing games for the iPhone and in record time.</p><p>Android is really going to have to make major market grabs over the next year in key demographics for the Game publishers to invest in developing for it when it means moving over to a whole new language and new dev environment aka Java.</p></htmltext>
<tokenext>How many game developers know Java ?
General purpose developers do n't count... sure they could make a simple logic game and add fancy graphics on top but something like Super Monkey Ball ? I do n't recall seeing any commercial games written in Java ever .
In this scenario , why would a game developer choose to write games in a language completely different from C + + when there is Obj-C which has the similarity right there in the name.. sure it 's not C + + but that does n't seemed to have stopped ALL of the major game dev companies from releasing games for the iPhone and in record time.Android is really going to have to make major market grabs over the next year in key demographics for the Game publishers to invest in developing for it when it means moving over to a whole new language and new dev environment aka Java .</tokentext>
<sentencetext>How many game developers know Java?
General purpose developers don't count... sure they could make a simple logic game and add fancy graphics on top but something like Super Monkey Ball?I don't recall seeing any commercial games written in Java ever.
In this scenario, why would a game developer choose to write games in a language completely different from C++ when there is Obj-C which has the similarity right there in the name.. sure it's not C++ but that doesn't seemed to have stopped ALL of the major game dev companies from releasing games for the iPhone and in record time.Android is really going to have to make major market grabs over the next year in key demographics for the Game publishers to invest in developing for it when it means moving over to a whole new language and new dev environment aka Java.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743607</id>
	<title>Extending your analogy</title>
	<author>Comboman</author>
	<datestamp>1255530300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>However, you aren't forced to buy Windows games only from the Windows Store(TM) where each game must be approved by Microsoft before you can buy it.  If that were the case, developing games for Mac would suddenly start to look at lot more appealing, in spite of the smaller installed base.</htmltext>
<tokenext>However , you are n't forced to buy Windows games only from the Windows Store ( TM ) where each game must be approved by Microsoft before you can buy it .
If that were the case , developing games for Mac would suddenly start to look at lot more appealing , in spite of the smaller installed base .</tokentext>
<sentencetext>However, you aren't forced to buy Windows games only from the Windows Store(TM) where each game must be approved by Microsoft before you can buy it.
If that were the case, developing games for Mac would suddenly start to look at lot more appealing, in spite of the smaller installed base.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743947</id>
	<title>More Work?</title>
	<author>BiggoronSword</author>
	<datestamp>1255531800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>FTA:<blockquote><div><p>One advantage of programming for the iPhone is not having to worry (much) about hardware compatibility. This could potentially be a problem for Android game developers as new handsets emerge. The possibility of a backlash exists if users buy a new Android smartphone only to find that the most popular games in the market don't render properly on their screen, or that the control scheme for the game doesn't work. A developer can try to work their way around these issues by designing for multiple screen resolutions and including multiple input methods, <strong>but this of course means extra work</strong>.</p></div></blockquote><p>How is this any different from application development on PCs?  It's really hard for me as a developer to feel remorse for a mobile application developer when it comes to backwards compatibility.</p><p>Clearly define what your hardware requirements are for your application.  If the user doesn't comply, it's their own fault.  Nothing new here.</p></div>
	</htmltext>
<tokenext>FTA : One advantage of programming for the iPhone is not having to worry ( much ) about hardware compatibility .
This could potentially be a problem for Android game developers as new handsets emerge .
The possibility of a backlash exists if users buy a new Android smartphone only to find that the most popular games in the market do n't render properly on their screen , or that the control scheme for the game does n't work .
A developer can try to work their way around these issues by designing for multiple screen resolutions and including multiple input methods , but this of course means extra work.How is this any different from application development on PCs ?
It 's really hard for me as a developer to feel remorse for a mobile application developer when it comes to backwards compatibility.Clearly define what your hardware requirements are for your application .
If the user does n't comply , it 's their own fault .
Nothing new here .</tokentext>
<sentencetext>FTA:One advantage of programming for the iPhone is not having to worry (much) about hardware compatibility.
This could potentially be a problem for Android game developers as new handsets emerge.
The possibility of a backlash exists if users buy a new Android smartphone only to find that the most popular games in the market don't render properly on their screen, or that the control scheme for the game doesn't work.
A developer can try to work their way around these issues by designing for multiple screen resolutions and including multiple input methods, but this of course means extra work.How is this any different from application development on PCs?
It's really hard for me as a developer to feel remorse for a mobile application developer when it comes to backwards compatibility.Clearly define what your hardware requirements are for your application.
If the user doesn't comply, it's their own fault.
Nothing new here.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881</id>
	<title>Trendy</title>
	<author>Nerdfest</author>
	<datestamp>1255524060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You can use logic all you want to show the advantages Android phones have, but until the shine wears off for the iPhone fans and people realize just how tied their hands are, it will remain the dominant phone. Really, the average user doesn't even care, although they usually realize later that they should have.  The article that predicted 2012 for Android to surpass the iPhone is probably accurate, or perhaps even early.</htmltext>
<tokenext>You can use logic all you want to show the advantages Android phones have , but until the shine wears off for the iPhone fans and people realize just how tied their hands are , it will remain the dominant phone .
Really , the average user does n't even care , although they usually realize later that they should have .
The article that predicted 2012 for Android to surpass the iPhone is probably accurate , or perhaps even early .</tokentext>
<sentencetext>You can use logic all you want to show the advantages Android phones have, but until the shine wears off for the iPhone fans and people realize just how tied their hands are, it will remain the dominant phone.
Really, the average user doesn't even care, although they usually realize later that they should have.
The article that predicted 2012 for Android to surpass the iPhone is probably accurate, or perhaps even early.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</id>
	<title>opinion</title>
	<author>Anonymous</author>
	<datestamp>1255522500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>I think that Android's future depends not on Google but on the devices that run it. Apple has the advantage of controlling both the platform and the device. So you know that whatever you develop for the iPhone it will work. But Android resembles more the PC market where there are different memory capacities, 3d acceleration or not, multi touch or not, keyboard or not, etc. That's why I don't play games on my PC and I bought a separate games console. Because I don't want to care about requirements.</htmltext>
<tokenext>I think that Android 's future depends not on Google but on the devices that run it .
Apple has the advantage of controlling both the platform and the device .
So you know that whatever you develop for the iPhone it will work .
But Android resembles more the PC market where there are different memory capacities , 3d acceleration or not , multi touch or not , keyboard or not , etc .
That 's why I do n't play games on my PC and I bought a separate games console .
Because I do n't want to care about requirements .</tokentext>
<sentencetext>I think that Android's future depends not on Google but on the devices that run it.
Apple has the advantage of controlling both the platform and the device.
So you know that whatever you develop for the iPhone it will work.
But Android resembles more the PC market where there are different memory capacities, 3d acceleration or not, multi touch or not, keyboard or not, etc.
That's why I don't play games on my PC and I bought a separate games console.
Because I don't want to care about requirements.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743099</id>
	<title>Re:Trendy</title>
	<author>Beyond\_GoodandEvil</author>
	<datestamp>1255526400000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>You can use logic all you want to show the advantages Android phones have, but until the shine wears off for the iPhone fans and people realize just how tied their hands are, it will remain the dominant phone.</i> <br>You're half right, the other part of the shine equation is eventually, the air of exclusivity will wear off and apple will become the next burberry and chavs will have them and then no one will want one.</p></htmltext>
<tokenext>You can use logic all you want to show the advantages Android phones have , but until the shine wears off for the iPhone fans and people realize just how tied their hands are , it will remain the dominant phone .
You 're half right , the other part of the shine equation is eventually , the air of exclusivity will wear off and apple will become the next burberry and chavs will have them and then no one will want one .</tokentext>
<sentencetext>You can use logic all you want to show the advantages Android phones have, but until the shine wears off for the iPhone fans and people realize just how tied their hands are, it will remain the dominant phone.
You're half right, the other part of the shine equation is eventually, the air of exclusivity will wear off and apple will become the next burberry and chavs will have them and then no one will want one.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743051</id>
	<title>Re:Objective C Java</title>
	<author>Clarious</author>
	<datestamp>1255525680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maybe because there are more Java programmers than Objective C ones?</p></htmltext>
<tokenext>Maybe because there are more Java programmers than Objective C ones ?</tokentext>
<sentencetext>Maybe because there are more Java programmers than Objective C ones?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742885</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744621</id>
	<title>Google is the new Microsoft, but Apple is the same</title>
	<author>Fdisk81</author>
	<datestamp>1255534740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Once again, Apple shoots itself in the foot with their closed architecture and rigurous standards. With Tegra and Snapdragon coming to Android devices Apple is going to lose the hardware edge it has right now on Android devices and be left with no edge other than the "cool" factor; I'm not claiming the iPhone is going down in flames, it'll still do well.  However, in terms of market share it will definitely go down to 3rd or 4th place in the market.

I'm not an Apple hater, their products are solid, albeit overpriced.  I am a proud Android user, I had the choice between the two devices and I went with a G1 over an iPhone because I saw its potential to become the top dog in the mobile market.

Is Apple wrong to stick to its mentality? I wouldn't say that necessarily, they've enjoyed the No. 2 spot and laughed themselves to the bank every year while enjoying consumer popularity as opposed to the usual Microsoft hatefest.</htmltext>
<tokenext>Once again , Apple shoots itself in the foot with their closed architecture and rigurous standards .
With Tegra and Snapdragon coming to Android devices Apple is going to lose the hardware edge it has right now on Android devices and be left with no edge other than the " cool " factor ; I 'm not claiming the iPhone is going down in flames , it 'll still do well .
However , in terms of market share it will definitely go down to 3rd or 4th place in the market .
I 'm not an Apple hater , their products are solid , albeit overpriced .
I am a proud Android user , I had the choice between the two devices and I went with a G1 over an iPhone because I saw its potential to become the top dog in the mobile market .
Is Apple wrong to stick to its mentality ?
I would n't say that necessarily , they 've enjoyed the No .
2 spot and laughed themselves to the bank every year while enjoying consumer popularity as opposed to the usual Microsoft hatefest .</tokentext>
<sentencetext>Once again, Apple shoots itself in the foot with their closed architecture and rigurous standards.
With Tegra and Snapdragon coming to Android devices Apple is going to lose the hardware edge it has right now on Android devices and be left with no edge other than the "cool" factor; I'm not claiming the iPhone is going down in flames, it'll still do well.
However, in terms of market share it will definitely go down to 3rd or 4th place in the market.
I'm not an Apple hater, their products are solid, albeit overpriced.
I am a proud Android user, I had the choice between the two devices and I went with a G1 over an iPhone because I saw its potential to become the top dog in the mobile market.
Is Apple wrong to stick to its mentality?
I wouldn't say that necessarily, they've enjoyed the No.
2 spot and laughed themselves to the bank every year while enjoying consumer popularity as opposed to the usual Microsoft hatefest.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29755285</id>
	<title>Re:opinion</title>
	<author>Dal Platinum</author>
	<datestamp>1255610460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is the first first post I've EVER seen on slashdot that is both appropriate, and accurate.</p><p>The lack of a physical standard is going to be the biggest problem.  Hell, even a choice of 3-4 standards would be better (numpad&amp;no-touch/touch&amp;homebutton/sliderkeyboard/joystick&amp;touch).  There are simply too many hardware options, and it's still a new phone, imagine what it will be like in two years, when I'm going to be alooking for a new phone.  WinMo has the same problem.</p><p>The other problem is the lack of quality control on the store.  I could probably knock up an Android app that will upload user contact details to my secret stash, and hide that beneath an app that just downloads pictures of girls in bikinis.  Restricting app access to user data is one of the benefits of a locked-down, app-approving environment.  Information may want to be free, but when it's MY information, I want that shit locked down.</p></htmltext>
<tokenext>This is the first first post I 've EVER seen on slashdot that is both appropriate , and accurate.The lack of a physical standard is going to be the biggest problem .
Hell , even a choice of 3-4 standards would be better ( numpad&amp;no-touch/touch&amp;homebutton/sliderkeyboard/joystick&amp;touch ) .
There are simply too many hardware options , and it 's still a new phone , imagine what it will be like in two years , when I 'm going to be alooking for a new phone .
WinMo has the same problem.The other problem is the lack of quality control on the store .
I could probably knock up an Android app that will upload user contact details to my secret stash , and hide that beneath an app that just downloads pictures of girls in bikinis .
Restricting app access to user data is one of the benefits of a locked-down , app-approving environment .
Information may want to be free , but when it 's MY information , I want that shit locked down .</tokentext>
<sentencetext>This is the first first post I've EVER seen on slashdot that is both appropriate, and accurate.The lack of a physical standard is going to be the biggest problem.
Hell, even a choice of 3-4 standards would be better (numpad&amp;no-touch/touch&amp;homebutton/sliderkeyboard/joystick&amp;touch).
There are simply too many hardware options, and it's still a new phone, imagine what it will be like in two years, when I'm going to be alooking for a new phone.
WinMo has the same problem.The other problem is the lack of quality control on the store.
I could probably knock up an Android app that will upload user contact details to my secret stash, and hide that beneath an app that just downloads pictures of girls in bikinis.
Restricting app access to user data is one of the benefits of a locked-down, app-approving environment.
Information may want to be free, but when it's MY information, I want that shit locked down.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743945</id>
	<title>Language is not an issue.</title>
	<author>FellowConspirator</author>
	<datestamp>1255531800000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>The statement "given Android programming is much easier (far more programmers know Java than Objective C)" is nonsensical. True enough that Java is popular, but Objective-C is trivial to learn. Actually the languages themselves don't have much bearing on the ease of development for the two platforms. It's the APIs. I've recently started messing around with Objective-C and Apple's Cocoa, and the language itself is VERY easy to pick up (and I'm not a professional developer s much as a person that uses programming as part of his job). The Cocoa API, however, is another kettle of fish. Not that Cocoa isn't well designed -- it's astonishingly well designed -- but, it's huge. Java is similar in that the language is relatively simple (on par with Obj-C, more or less), but you've got LOTS of APIs to learn.</p><p>I suspect that if you are a game developer, you're probably making little use of most of the APIs, and if you are big enough, I'm sure that you use a toolkit that abstracts-away the underlying platform. In either case, the primary language used probably has little bearing on the ease of development of games on either platform.</p></htmltext>
<tokenext>The statement " given Android programming is much easier ( far more programmers know Java than Objective C ) " is nonsensical .
True enough that Java is popular , but Objective-C is trivial to learn .
Actually the languages themselves do n't have much bearing on the ease of development for the two platforms .
It 's the APIs .
I 've recently started messing around with Objective-C and Apple 's Cocoa , and the language itself is VERY easy to pick up ( and I 'm not a professional developer s much as a person that uses programming as part of his job ) .
The Cocoa API , however , is another kettle of fish .
Not that Cocoa is n't well designed -- it 's astonishingly well designed -- but , it 's huge .
Java is similar in that the language is relatively simple ( on par with Obj-C , more or less ) , but you 've got LOTS of APIs to learn.I suspect that if you are a game developer , you 're probably making little use of most of the APIs , and if you are big enough , I 'm sure that you use a toolkit that abstracts-away the underlying platform .
In either case , the primary language used probably has little bearing on the ease of development of games on either platform .</tokentext>
<sentencetext>The statement "given Android programming is much easier (far more programmers know Java than Objective C)" is nonsensical.
True enough that Java is popular, but Objective-C is trivial to learn.
Actually the languages themselves don't have much bearing on the ease of development for the two platforms.
It's the APIs.
I've recently started messing around with Objective-C and Apple's Cocoa, and the language itself is VERY easy to pick up (and I'm not a professional developer s much as a person that uses programming as part of his job).
The Cocoa API, however, is another kettle of fish.
Not that Cocoa isn't well designed -- it's astonishingly well designed -- but, it's huge.
Java is similar in that the language is relatively simple (on par with Obj-C, more or less), but you've got LOTS of APIs to learn.I suspect that if you are a game developer, you're probably making little use of most of the APIs, and if you are big enough, I'm sure that you use a toolkit that abstracts-away the underlying platform.
In either case, the primary language used probably has little bearing on the ease of development of games on either platform.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744601</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>OwMyBrain</author>
	<datestamp>1255534680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The appeal of iPhone/Android development is not about gaining market share against the PC game market. It's that independent developers can make quality apps cheaply.</p><p>Developing and publishing a PC game is expensive. Even though digital distribution systems such as Steam are making it cheaper for independent game companies it is still very difficult for an individual to create a PC game that can compete with today's AAAAA titles.</p><p>However, no one expects to be playing AAAAA titles on their phone (at least not yet, anyway). That means games for these mobile platforms need not be grandiose explosions of eye candy, simply because the hardware isn't there (yet). That's great news for the Indie developer who could create a fun, lightweight, addictive game, and do it in his spare time.</p><p>When the barrier to entry into a market is small like this, we will see a lot of new players, which will lead to new ideas, competition, and true innovation. So yes, the "wide-open field" is terribly accurate. That's what makes this all the more exciting.</p><p>For individuals it isn't going to be about market share, because if I can spend $25 bucks and a few weekends to build an app that I make $100 off of, then it's worth it to me. It's a great addition to my resume and some beer money. "Market share" is a term for board members trying to maximize their effectiveness, not developers trying to create something new and interesting.</p></htmltext>
<tokenext>The appeal of iPhone/Android development is not about gaining market share against the PC game market .
It 's that independent developers can make quality apps cheaply.Developing and publishing a PC game is expensive .
Even though digital distribution systems such as Steam are making it cheaper for independent game companies it is still very difficult for an individual to create a PC game that can compete with today 's AAAAA titles.However , no one expects to be playing AAAAA titles on their phone ( at least not yet , anyway ) .
That means games for these mobile platforms need not be grandiose explosions of eye candy , simply because the hardware is n't there ( yet ) .
That 's great news for the Indie developer who could create a fun , lightweight , addictive game , and do it in his spare time.When the barrier to entry into a market is small like this , we will see a lot of new players , which will lead to new ideas , competition , and true innovation .
So yes , the " wide-open field " is terribly accurate .
That 's what makes this all the more exciting.For individuals it is n't going to be about market share , because if I can spend $ 25 bucks and a few weekends to build an app that I make $ 100 off of , then it 's worth it to me .
It 's a great addition to my resume and some beer money .
" Market share " is a term for board members trying to maximize their effectiveness , not developers trying to create something new and interesting .</tokentext>
<sentencetext>The appeal of iPhone/Android development is not about gaining market share against the PC game market.
It's that independent developers can make quality apps cheaply.Developing and publishing a PC game is expensive.
Even though digital distribution systems such as Steam are making it cheaper for independent game companies it is still very difficult for an individual to create a PC game that can compete with today's AAAAA titles.However, no one expects to be playing AAAAA titles on their phone (at least not yet, anyway).
That means games for these mobile platforms need not be grandiose explosions of eye candy, simply because the hardware isn't there (yet).
That's great news for the Indie developer who could create a fun, lightweight, addictive game, and do it in his spare time.When the barrier to entry into a market is small like this, we will see a lot of new players, which will lead to new ideas, competition, and true innovation.
So yes, the "wide-open field" is terribly accurate.
That's what makes this all the more exciting.For individuals it isn't going to be about market share, because if I can spend $25 bucks and a few weekends to build an app that I make $100 off of, then it's worth it to me.
It's a great addition to my resume and some beer money.
"Market share" is a term for board members trying to maximize their effectiveness, not developers trying to create something new and interesting.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744303</id>
	<title>Re:opinion</title>
	<author>mdwh2</author>
	<datestamp>1255533420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>It might create more barrier for an indie developer to entry the market because they have to test their software on all the supported devices and make adjustments, but for studios it's not so much work.</i></p><p>Indeed, but to add to that, it's <i>far less work that porting to another platform such as the Iphone</i>.</p><p>A developer can pick whatever phone they like to develop for. If it turns out that some of those share a common platform (such as Windows, Android, etc) that make it relatively easy to run on other devices, in no way is that a bad thing. It makes it a lot easier to port than it would if you'd picked the Iphone - and even if you don't care about that, you're certainly not worse off...</p><p>Once again, Apple fans spin a negative point (every phone being incompatible with it) into somehow being something good.</p></htmltext>
<tokenext>It might create more barrier for an indie developer to entry the market because they have to test their software on all the supported devices and make adjustments , but for studios it 's not so much work.Indeed , but to add to that , it 's far less work that porting to another platform such as the Iphone.A developer can pick whatever phone they like to develop for .
If it turns out that some of those share a common platform ( such as Windows , Android , etc ) that make it relatively easy to run on other devices , in no way is that a bad thing .
It makes it a lot easier to port than it would if you 'd picked the Iphone - and even if you do n't care about that , you 're certainly not worse off...Once again , Apple fans spin a negative point ( every phone being incompatible with it ) into somehow being something good .</tokentext>
<sentencetext>It might create more barrier for an indie developer to entry the market because they have to test their software on all the supported devices and make adjustments, but for studios it's not so much work.Indeed, but to add to that, it's far less work that porting to another platform such as the Iphone.A developer can pick whatever phone they like to develop for.
If it turns out that some of those share a common platform (such as Windows, Android, etc) that make it relatively easy to run on other devices, in no way is that a bad thing.
It makes it a lot easier to port than it would if you'd picked the Iphone - and even if you don't care about that, you're certainly not worse off...Once again, Apple fans spin a negative point (every phone being incompatible with it) into somehow being something good.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742875</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29754143</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>mjwx</author>
	<datestamp>1255638060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Twenty years ago, in Europe, the PC was a dull machine that you only ever ran business applications on.</p></div> </blockquote><p>

20 years ago in Australia (1989) there was a great deal of cross platform programming in games, retail games were designed to work on DOS and Commodore 64. Fast forward 3 years and we have Windows, this is where the great DOS gaming golden age started. Your Wolfenstiens, Commander Keen's, Duke Nukems, Space/police Quests (I miss the adventure game, well there's always GOG.com). PC gaming was semi-entrenched in 1989 but was firmly entrenched in 1992.<br> <br>

As far as gaming is concerned, Microsoft doesn't need to worry, Mac's will never be good enough for PC games with their fixed and limited hardware spec's. Consoles only need to worry about PC's (if your name is not Nintendo). Only the mobile gaming platforms need to be concerned and Nintendo and Sony are not worried about the iphone, the DS and PSP have a large enough back catalogue that the few ancient PC games that have been hurriedly ported to the iphone do not matter, secondly this platform has not proven profitable yet, thirdly the DS and PSP have been competing with mobile phone games in Japan for years and it hasn't affected their sales one iota. It is Asia where mobile gaming is big and the iphone is only really big in the West where mobile gaming isn't.</p><blockquote><div><p>So, given Android programming is much easier (far more programmers know Java than Objective C),</p></div></blockquote><p>

I'm a bit of an android fan but this is subjective. Android also supports C in some capacity now as well.

As for easier to develop for, the actual coding is easier on iphone but end to end, planning, coding, marketing and releasing is far easier on Android due to Apple's extremist limitations on the iphone. Android has also give greater latitude to developers with what they can do with the device, more access to API's not to mention the OS itself so by the simple fact that you can do more with Android means that development for Android can easily become more difficult. As for coding "hello world" that would depend, as you said on whether your an objective C or Java developer.</p><blockquote><div><p>All it would take is one damn good phone running Android to topple Apple off its perch.</p></div></blockquote><p>

Or one cheaper "good enough" phone. Every iphone owner who is not a fanboy openly admits that Android is a better operating system and they would have got one if it was the same price as the iphone. Most people dont care about Android or Iphone and will just buy the best phone they can afford, if the HTC magic (myTouch3G for our American friends) had of been $5 cheaper per month then the iphone we'd see a great deal more Android adoption here in Australia.</p></div>
	</htmltext>
<tokenext>Twenty years ago , in Europe , the PC was a dull machine that you only ever ran business applications on .
20 years ago in Australia ( 1989 ) there was a great deal of cross platform programming in games , retail games were designed to work on DOS and Commodore 64 .
Fast forward 3 years and we have Windows , this is where the great DOS gaming golden age started .
Your Wolfenstiens , Commander Keen 's , Duke Nukems , Space/police Quests ( I miss the adventure game , well there 's always GOG.com ) .
PC gaming was semi-entrenched in 1989 but was firmly entrenched in 1992 .
As far as gaming is concerned , Microsoft does n't need to worry , Mac 's will never be good enough for PC games with their fixed and limited hardware spec 's .
Consoles only need to worry about PC 's ( if your name is not Nintendo ) .
Only the mobile gaming platforms need to be concerned and Nintendo and Sony are not worried about the iphone , the DS and PSP have a large enough back catalogue that the few ancient PC games that have been hurriedly ported to the iphone do not matter , secondly this platform has not proven profitable yet , thirdly the DS and PSP have been competing with mobile phone games in Japan for years and it has n't affected their sales one iota .
It is Asia where mobile gaming is big and the iphone is only really big in the West where mobile gaming is n't.So , given Android programming is much easier ( far more programmers know Java than Objective C ) , I 'm a bit of an android fan but this is subjective .
Android also supports C in some capacity now as well .
As for easier to develop for , the actual coding is easier on iphone but end to end , planning , coding , marketing and releasing is far easier on Android due to Apple 's extremist limitations on the iphone .
Android has also give greater latitude to developers with what they can do with the device , more access to API 's not to mention the OS itself so by the simple fact that you can do more with Android means that development for Android can easily become more difficult .
As for coding " hello world " that would depend , as you said on whether your an objective C or Java developer.All it would take is one damn good phone running Android to topple Apple off its perch .
Or one cheaper " good enough " phone .
Every iphone owner who is not a fanboy openly admits that Android is a better operating system and they would have got one if it was the same price as the iphone .
Most people dont care about Android or Iphone and will just buy the best phone they can afford , if the HTC magic ( myTouch3G for our American friends ) had of been $ 5 cheaper per month then the iphone we 'd see a great deal more Android adoption here in Australia .</tokentext>
<sentencetext>Twenty years ago, in Europe, the PC was a dull machine that you only ever ran business applications on.
20 years ago in Australia (1989) there was a great deal of cross platform programming in games, retail games were designed to work on DOS and Commodore 64.
Fast forward 3 years and we have Windows, this is where the great DOS gaming golden age started.
Your Wolfenstiens, Commander Keen's, Duke Nukems, Space/police Quests (I miss the adventure game, well there's always GOG.com).
PC gaming was semi-entrenched in 1989 but was firmly entrenched in 1992.
As far as gaming is concerned, Microsoft doesn't need to worry, Mac's will never be good enough for PC games with their fixed and limited hardware spec's.
Consoles only need to worry about PC's (if your name is not Nintendo).
Only the mobile gaming platforms need to be concerned and Nintendo and Sony are not worried about the iphone, the DS and PSP have a large enough back catalogue that the few ancient PC games that have been hurriedly ported to the iphone do not matter, secondly this platform has not proven profitable yet, thirdly the DS and PSP have been competing with mobile phone games in Japan for years and it hasn't affected their sales one iota.
It is Asia where mobile gaming is big and the iphone is only really big in the West where mobile gaming isn't.So, given Android programming is much easier (far more programmers know Java than Objective C),

I'm a bit of an android fan but this is subjective.
Android also supports C in some capacity now as well.
As for easier to develop for, the actual coding is easier on iphone but end to end, planning, coding, marketing and releasing is far easier on Android due to Apple's extremist limitations on the iphone.
Android has also give greater latitude to developers with what they can do with the device, more access to API's not to mention the OS itself so by the simple fact that you can do more with Android means that development for Android can easily become more difficult.
As for coding "hello world" that would depend, as you said on whether your an objective C or Java developer.All it would take is one damn good phone running Android to topple Apple off its perch.
Or one cheaper "good enough" phone.
Every iphone owner who is not a fanboy openly admits that Android is a better operating system and they would have got one if it was the same price as the iphone.
Most people dont care about Android or Iphone and will just buy the best phone they can afford, if the HTC magic (myTouch3G for our American friends) had of been $5 cheaper per month then the iphone we'd see a great deal more Android adoption here in Australia.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743165</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>Anonymous</author>
	<datestamp>1255527240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think you are underestimating the iPhone ecosystem. It is big, bold and in your face. Even my folks know about the app-store. When the "We've got an app for that" parodies got out there, you know the clock was ticking for Android. The G1's been out for a year, and I don't know anyone with one. All I can say, disappointing...</p></htmltext>
<tokenext>I think you are underestimating the iPhone ecosystem .
It is big , bold and in your face .
Even my folks know about the app-store .
When the " We 've got an app for that " parodies got out there , you know the clock was ticking for Android .
The G1 's been out for a year , and I do n't know anyone with one .
All I can say , disappointing.. .</tokentext>
<sentencetext>I think you are underestimating the iPhone ecosystem.
It is big, bold and in your face.
Even my folks know about the app-store.
When the "We've got an app for that" parodies got out there, you know the clock was ticking for Android.
The G1's been out for a year, and I don't know anyone with one.
All I can say, disappointing...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29755919</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>KitsuneSoftware</author>
	<datestamp>1255615380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No commercial games? How about RuneScape, which has spent the last two years hovering around a million paying subscribers? Almost all of it (client and back end, but not hardware acceleration) is written in Java.</htmltext>
<tokenext>No commercial games ?
How about RuneScape , which has spent the last two years hovering around a million paying subscribers ?
Almost all of it ( client and back end , but not hardware acceleration ) is written in Java .</tokentext>
<sentencetext>No commercial games?
How about RuneScape, which has spent the last two years hovering around a million paying subscribers?
Almost all of it (client and back end, but not hardware acceleration) is written in Java.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744515</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29747825</id>
	<title>Re:Seems a trifle disingenuous to me</title>
	<author>day2day</author>
	<datestamp>1255548360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's the fight to own the living room.  Lot's of opportunities there.  You can already stream Netflix and I'm sure we'll see other direct competition with the cable companies soon.</htmltext>
<tokenext>It 's the fight to own the living room .
Lot 's of opportunities there .
You can already stream Netflix and I 'm sure we 'll see other direct competition with the cable companies soon .</tokentext>
<sentencetext>It's the fight to own the living room.
Lot's of opportunities there.
You can already stream Netflix and I'm sure we'll see other direct competition with the cable companies soon.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743341</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743099
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742925
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744251
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743527
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743389
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743051
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742885
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743945
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744145
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744163
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743229
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29747825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744007
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744219
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743579
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744121
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744077
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743165
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29753705
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746301
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744015
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29748823
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29754143
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29745519
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744515
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743799
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744601
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743405
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744369
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29751815
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746313
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744303
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742875
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29745895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743369
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743607
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29755919
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744515
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_0511259_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29755285
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_0511259.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742881
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743099
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744077
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743229
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_0511259.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742847
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742987
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743389
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744121
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29745895
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29754143
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743579
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743165
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743405
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744515
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29745519
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29755919
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29748823
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744163
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743341
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29747825
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744007
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744219
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743945
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746313
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743799
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744369
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743607
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743369
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744601
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_0511259.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743947
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_0511259.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742771
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29755285
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744251
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743527
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744015
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29751815
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742925
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744145
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742875
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29744303
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_0511259.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29746301
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29753705
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_0511259.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742885
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29743051
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_0511259.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_0511259.29742911
</commentlist>
</conversation>
