<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_01_12_001207</id>
	<title>An Android Developer's Top 10 Gripes</title>
	<author>kdawson</author>
	<datestamp>1263301560000</datestamp>
	<htmltext>gkunene writes in with the plaint of a veteran mobile application developer who vents his frustration with a list of <a href="http://www.developer.com/ws/article.php/3857796/An-Android-Developers-Top-10-Gripes.htm">10 things he loves to hate about Android</a>. <i>"1. Open Source. Leave it to Google to place all the code for their handset platform in the hands of the masses. Not only does this mean anyone can download and roll a new version of their phone firmware, but it also means absolutely any maker can roll its own Android device. ... After all's said and done, I really must admit that Android, despite its relatively few flaws, is one of my favorite platforms to work with. Quite honestly, if my complaint about how the word 'Intent' makes for awkward grammatical constructions ranks in the top 10, I'd say the Android platform is doing pretty well for itself."</i></htmltext>
<tokenext>gkunene writes in with the plaint of a veteran mobile application developer who vents his frustration with a list of 10 things he loves to hate about Android .
" 1. Open Source .
Leave it to Google to place all the code for their handset platform in the hands of the masses .
Not only does this mean anyone can download and roll a new version of their phone firmware , but it also means absolutely any maker can roll its own Android device .
... After all 's said and done , I really must admit that Android , despite its relatively few flaws , is one of my favorite platforms to work with .
Quite honestly , if my complaint about how the word 'Intent ' makes for awkward grammatical constructions ranks in the top 10 , I 'd say the Android platform is doing pretty well for itself .
"</tokentext>
<sentencetext>gkunene writes in with the plaint of a veteran mobile application developer who vents his frustration with a list of 10 things he loves to hate about Android.
"1. Open Source.
Leave it to Google to place all the code for their handset platform in the hands of the masses.
Not only does this mean anyone can download and roll a new version of their phone firmware, but it also means absolutely any maker can roll its own Android device.
... After all's said and done, I really must admit that Android, despite its relatively few flaws, is one of my favorite platforms to work with.
Quite honestly, if my complaint about how the word 'Intent' makes for awkward grammatical constructions ranks in the top 10, I'd say the Android platform is doing pretty well for itself.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737896</id>
	<title>Its called "sarcasm"</title>
	<author>Anonymous</author>
	<datestamp>1263314940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>LEARN IT, BITCH.</p></htmltext>
<tokenext>LEARN IT , BITCH .</tokentext>
<sentencetext>LEARN IT, BITCH.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743882</id>
	<title>Re:Lack of support for wi-fi proxy</title>
	<author>Anonymous</author>
	<datestamp>1263296400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Android also needs a good model for connecting to multiple VPNs.  This is something that Windows Mobile handles robustly.  I can connect to a secure wireless network, then fire up a VPN client, so all my communication is tunneled to the corporate site.</p><p>This, I can't do under Android, yet.  And until this is not just doable, there will be issues with this platform in the enterprise.</p><p>I have high hopes though.  Android has gotten very far in the past 14 months since the G1 was released.  I'm sure that Google should have support for encryption and robust VPN clients by 3.0.</p><p>Worst cast, one will find a custom ROM with Linux kernel modules, and one would just manually do this stuff the age old way, PPP over ssh, or pptp.</p></htmltext>
<tokenext>Android also needs a good model for connecting to multiple VPNs .
This is something that Windows Mobile handles robustly .
I can connect to a secure wireless network , then fire up a VPN client , so all my communication is tunneled to the corporate site.This , I ca n't do under Android , yet .
And until this is not just doable , there will be issues with this platform in the enterprise.I have high hopes though .
Android has gotten very far in the past 14 months since the G1 was released .
I 'm sure that Google should have support for encryption and robust VPN clients by 3.0.Worst cast , one will find a custom ROM with Linux kernel modules , and one would just manually do this stuff the age old way , PPP over ssh , or pptp .</tokentext>
<sentencetext>Android also needs a good model for connecting to multiple VPNs.
This is something that Windows Mobile handles robustly.
I can connect to a secure wireless network, then fire up a VPN client, so all my communication is tunneled to the corporate site.This, I can't do under Android, yet.
And until this is not just doable, there will be issues with this platform in the enterprise.I have high hopes though.
Android has gotten very far in the past 14 months since the G1 was released.
I'm sure that Google should have support for encryption and robust VPN clients by 3.0.Worst cast, one will find a custom ROM with Linux kernel modules, and one would just manually do this stuff the age old way, PPP over ssh, or pptp.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738176</id>
	<title>Re:why Java?</title>
	<author>DrXym</author>
	<datestamp>1263315900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>2) You cannot build once run everywhere. Its a myth. With J2ME phones, devs test and optimize for every supported handset, and it will be the same for Android.</i>
<p>
It isn't a myth, at least not for desktop profile apps and higher. I regularly build Java applications exclusively on one platform and encounter minimal issues when they run on a completely different platform. Usually when these problems occur they are my own fault - path issues and the like.
</p><p>
Even on embedded devices such as J2ME, as long as you code to the relevant profile you stand a reasonable chance of your app running on other devices that comply to that profile. Even if you do encounter problems I guarantee you they are an order less complex than having to rebuild, repackage and redeploy binary executables for disparate platforms.
</p><p>
It certainly wouldn't hurt for Google (+ Android phone manufacturers) implementing some form of compliance testing because there would be nothing worse for the platform than if it shattered into dozens of semi compatible versions of the same thing.</p></htmltext>
<tokenext>2 ) You can not build once run everywhere .
Its a myth .
With J2ME phones , devs test and optimize for every supported handset , and it will be the same for Android .
It is n't a myth , at least not for desktop profile apps and higher .
I regularly build Java applications exclusively on one platform and encounter minimal issues when they run on a completely different platform .
Usually when these problems occur they are my own fault - path issues and the like .
Even on embedded devices such as J2ME , as long as you code to the relevant profile you stand a reasonable chance of your app running on other devices that comply to that profile .
Even if you do encounter problems I guarantee you they are an order less complex than having to rebuild , repackage and redeploy binary executables for disparate platforms .
It certainly would n't hurt for Google ( + Android phone manufacturers ) implementing some form of compliance testing because there would be nothing worse for the platform than if it shattered into dozens of semi compatible versions of the same thing .</tokentext>
<sentencetext>2) You cannot build once run everywhere.
Its a myth.
With J2ME phones, devs test and optimize for every supported handset, and it will be the same for Android.
It isn't a myth, at least not for desktop profile apps and higher.
I regularly build Java applications exclusively on one platform and encounter minimal issues when they run on a completely different platform.
Usually when these problems occur they are my own fault - path issues and the like.
Even on embedded devices such as J2ME, as long as you code to the relevant profile you stand a reasonable chance of your app running on other devices that comply to that profile.
Even if you do encounter problems I guarantee you they are an order less complex than having to rebuild, repackage and redeploy binary executables for disparate platforms.
It certainly wouldn't hurt for Google (+ Android phone manufacturers) implementing some form of compliance testing because there would be nothing worse for the platform than if it shattered into dozens of semi compatible versions of the same thing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737066</id>
	<title>It's supposed to be funny!</title>
	<author>Anonymous</author>
	<datestamp>1263311640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Retards.</p></htmltext>
<tokenext>Retards .</tokentext>
<sentencetext>Retards.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736594</id>
	<title>Re:What?</title>
	<author>furby076</author>
	<datestamp>1263309660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Disclaimer: I actually read the FA (yes, I know this is slashdot). This guy is angry because, amongst other things, Google has made 40\% of his debugging skills useless. Apperantly, his problem is that this means that other people without his "superskills" can develop software for Android.</p></div><p>I actually thought he was being facetious, more along the lines of "Darn you for buying me that lottery ticket that made me a millionaire".  Though if he billed hourly he is probably annoyed because he has 40\% less work<nobr> <wbr></nobr>:)</p></div>
	</htmltext>
<tokenext>Disclaimer : I actually read the FA ( yes , I know this is slashdot ) .
This guy is angry because , amongst other things , Google has made 40 \ % of his debugging skills useless .
Apperantly , his problem is that this means that other people without his " superskills " can develop software for Android.I actually thought he was being facetious , more along the lines of " Darn you for buying me that lottery ticket that made me a millionaire " .
Though if he billed hourly he is probably annoyed because he has 40 \ % less work : )</tokentext>
<sentencetext>Disclaimer: I actually read the FA (yes, I know this is slashdot).
This guy is angry because, amongst other things, Google has made 40\% of his debugging skills useless.
Apperantly, his problem is that this means that other people without his "superskills" can develop software for Android.I actually thought he was being facetious, more along the lines of "Darn you for buying me that lottery ticket that made me a millionaire".
Though if he billed hourly he is probably annoyed because he has 40\% less work :)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735968</id>
	<title>kdawson?</title>
	<author>dangitman</author>
	<datestamp>1263305760000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext>Yeah, you might want to go and die in an (Open Source) fire. Thanks for all the wonderful misleading summaries, dickbag.</htmltext>
<tokenext>Yeah , you might want to go and die in an ( Open Source ) fire .
Thanks for all the wonderful misleading summaries , dickbag .</tokentext>
<sentencetext>Yeah, you might want to go and die in an (Open Source) fire.
Thanks for all the wonderful misleading summaries, dickbag.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736706</id>
	<title>Re:dumb article/crappy developer</title>
	<author>entrigant</author>
	<datestamp>1263310200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's a problem with developers, and it annoys the piss out of me. There are a precious few apps that actually completely close when you hit menu -&gt; quit. Most don't, and many even lack a quit command altogether.</p><p>I don't know if it's because android is attracting developers that aren't use to multitasking on phones (e.g. iphone) so they don't even think of the need for a proper quit or if it's something else, but I hope they learn soon. I get tired of having to run a task manager to manually kill each app after I'm done using it.</p></htmltext>
<tokenext>It 's a problem with developers , and it annoys the piss out of me .
There are a precious few apps that actually completely close when you hit menu - &gt; quit .
Most do n't , and many even lack a quit command altogether.I do n't know if it 's because android is attracting developers that are n't use to multitasking on phones ( e.g .
iphone ) so they do n't even think of the need for a proper quit or if it 's something else , but I hope they learn soon .
I get tired of having to run a task manager to manually kill each app after I 'm done using it .</tokentext>
<sentencetext>It's a problem with developers, and it annoys the piss out of me.
There are a precious few apps that actually completely close when you hit menu -&gt; quit.
Most don't, and many even lack a quit command altogether.I don't know if it's because android is attracting developers that aren't use to multitasking on phones (e.g.
iphone) so they don't even think of the need for a proper quit or if it's something else, but I hope they learn soon.
I get tired of having to run a task manager to manually kill each app after I'm done using it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736674</id>
	<title>He Calls Himself an Android Developer?</title>
	<author>mrpacmanjel</author>
	<datestamp>1263310080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>1. Open Source<br>This is the most benign on this list, and it's only here because now everyone and their brother is going to make a new "Android-powered" device.</p></div><p>I'm tempted to quote the whole paragraph but this last bit made me laugh!<br>I thought this was a good thing because it means more competition, the "barrier to entry" is low - it's accessable to almost anyone and enables innovation.</p><p><div class="quote"><p>3. Device Debugging<nobr> <wbr></nobr>..Back in my day (and by "in my day," I mean two years ago..Why do I hate this extremely useful tool? I hate it because it makes about 40\% of my debugging skills nearly useless!..<br>curse their cotton socks, has quite literally taken a process that used to involve hours of work and reduced it to simply pressing F11. Not only is it straightforward and easy to use, but it also works on every platform out there (Mac, PC, and Linux).</p></div><p>He MUST be JOKING - must be!<br>No developer in thier right mind would see this as a bad thing!<br>Especially "Back in my day (and by "in my day," I mean two years ago)". This "wealth of experience" proves his naivety.</p><p><div class="quote"><p>6. Java--Thanks, But I'll Take It from Here<br>As a programmer, it makes me feel like I'm getting a very slow lobotomy..nearly impossible to, say, write an anti-aliased font library that renders in a reasonable amount of time..write custom libraries in C with their NDK, but now we're debugging two languages..</p></div><p>What a narrow-minded view!. Not everyone wants to write low-level stuff like an anti-aliased font library. The vm that "runs" the android platform is absolutely fine for every day stuff like email apps and "fart" applications!</p><p><div class="quote"><p>9. A General Lack of 'Evilness'<br>This lack of an iron grip (which both Apple and Verizon have effectively, if obnoxiously, employed on mobile developers) is exactly what is leading to the current and future fragmentation..Google, with luck, will learn when it's good to be evil</p><p>10. Hardware, Hardware, Hardware<br>The current crop of Android hardware, for lack of a better word, sucks..</p></div><p>He MUST be JOKING - must be!<br>He MUST be naive.<br>Quite frankly I have lost the will to comment further except</p><p><div class="quote"><p>I really must admit that Android, despite its relatively few flaws, is one of my favorite platforms to work with. Quite honestly, if my complaint about how the word 'Intent' makes for awkward grammatical constructions ranks in the top 10, I'd say the Android platform is doing pretty well for itself.</p></div><p>I hate to think what he could have said if he hated Android!</p><p>I'll give the guy the benefit of the doubt and some of these points are "tongue-in-cheek" - assuming that's the case then ok verrry funny!</p><p>I'm certainly not defending Google or an Android fanboy but this article is utter rubbish.</p><p>He should really go and develop for the iPhone or Windows mobile instead. Both these platforms are more aligned with his way of thinking!</p></div>
	</htmltext>
<tokenext>1 .
Open SourceThis is the most benign on this list , and it 's only here because now everyone and their brother is going to make a new " Android-powered " device.I 'm tempted to quote the whole paragraph but this last bit made me laugh ! I thought this was a good thing because it means more competition , the " barrier to entry " is low - it 's accessable to almost anyone and enables innovation.3 .
Device Debugging ..Back in my day ( and by " in my day , " I mean two years ago..Why do I hate this extremely useful tool ?
I hate it because it makes about 40 \ % of my debugging skills nearly useless ! ..curse their cotton socks , has quite literally taken a process that used to involve hours of work and reduced it to simply pressing F11 .
Not only is it straightforward and easy to use , but it also works on every platform out there ( Mac , PC , and Linux ) .He MUST be JOKING - must be ! No developer in thier right mind would see this as a bad thing ! Especially " Back in my day ( and by " in my day , " I mean two years ago ) " .
This " wealth of experience " proves his naivety.6 .
Java--Thanks , But I 'll Take It from HereAs a programmer , it makes me feel like I 'm getting a very slow lobotomy..nearly impossible to , say , write an anti-aliased font library that renders in a reasonable amount of time..write custom libraries in C with their NDK , but now we 're debugging two languages..What a narrow-minded view ! .
Not everyone wants to write low-level stuff like an anti-aliased font library .
The vm that " runs " the android platform is absolutely fine for every day stuff like email apps and " fart " applications ! 9 .
A General Lack of 'Evilness'This lack of an iron grip ( which both Apple and Verizon have effectively , if obnoxiously , employed on mobile developers ) is exactly what is leading to the current and future fragmentation..Google , with luck , will learn when it 's good to be evil10 .
Hardware , Hardware , HardwareThe current crop of Android hardware , for lack of a better word , sucks..He MUST be JOKING - must be ! He MUST be naive.Quite frankly I have lost the will to comment further exceptI really must admit that Android , despite its relatively few flaws , is one of my favorite platforms to work with .
Quite honestly , if my complaint about how the word 'Intent ' makes for awkward grammatical constructions ranks in the top 10 , I 'd say the Android platform is doing pretty well for itself.I hate to think what he could have said if he hated Android ! I 'll give the guy the benefit of the doubt and some of these points are " tongue-in-cheek " - assuming that 's the case then ok verrry funny ! I 'm certainly not defending Google or an Android fanboy but this article is utter rubbish.He should really go and develop for the iPhone or Windows mobile instead .
Both these platforms are more aligned with his way of thinking !</tokentext>
<sentencetext>1.
Open SourceThis is the most benign on this list, and it's only here because now everyone and their brother is going to make a new "Android-powered" device.I'm tempted to quote the whole paragraph but this last bit made me laugh!I thought this was a good thing because it means more competition, the "barrier to entry" is low - it's accessable to almost anyone and enables innovation.3.
Device Debugging ..Back in my day (and by "in my day," I mean two years ago..Why do I hate this extremely useful tool?
I hate it because it makes about 40\% of my debugging skills nearly useless!..curse their cotton socks, has quite literally taken a process that used to involve hours of work and reduced it to simply pressing F11.
Not only is it straightforward and easy to use, but it also works on every platform out there (Mac, PC, and Linux).He MUST be JOKING - must be!No developer in thier right mind would see this as a bad thing!Especially "Back in my day (and by "in my day," I mean two years ago)".
This "wealth of experience" proves his naivety.6.
Java--Thanks, But I'll Take It from HereAs a programmer, it makes me feel like I'm getting a very slow lobotomy..nearly impossible to, say, write an anti-aliased font library that renders in a reasonable amount of time..write custom libraries in C with their NDK, but now we're debugging two languages..What a narrow-minded view!.
Not everyone wants to write low-level stuff like an anti-aliased font library.
The vm that "runs" the android platform is absolutely fine for every day stuff like email apps and "fart" applications!9.
A General Lack of 'Evilness'This lack of an iron grip (which both Apple and Verizon have effectively, if obnoxiously, employed on mobile developers) is exactly what is leading to the current and future fragmentation..Google, with luck, will learn when it's good to be evil10.
Hardware, Hardware, HardwareThe current crop of Android hardware, for lack of a better word, sucks..He MUST be JOKING - must be!He MUST be naive.Quite frankly I have lost the will to comment further exceptI really must admit that Android, despite its relatively few flaws, is one of my favorite platforms to work with.
Quite honestly, if my complaint about how the word 'Intent' makes for awkward grammatical constructions ranks in the top 10, I'd say the Android platform is doing pretty well for itself.I hate to think what he could have said if he hated Android!I'll give the guy the benefit of the doubt and some of these points are "tongue-in-cheek" - assuming that's the case then ok verrry funny!I'm certainly not defending Google or an Android fanboy but this article is utter rubbish.He should really go and develop for the iPhone or Windows mobile instead.
Both these platforms are more aligned with his way of thinking!
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736270</id>
	<title>Re:dumb article/crappy developer</title>
	<author>PianoComp81</author>
	<datestamp>1263307740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Point 2. The Tyranny of the Activity</p><blockquote><div><p>Android, by contrast, pushes you to design everything as small, self- contained mini-applications</p></div></blockquote><p>

That sounds a bit like the old UNIX principle. And what's wrong with having applications that do small things and do it well. I don't want a picture application with it's own twitter functionality, I have a proper twitter client for that. etc.</p></div></blockquote><p>

The biggest reason he gives while this is bad is because it destroys then recreates an activity upon rotating the screen. What I've noticed on my droid is that application refresh the screen when the screen is rotated. To get around the refreshing, developers have to hack around google's API.</p></div>
	</htmltext>
<tokenext>Point 2 .
The Tyranny of the ActivityAndroid , by contrast , pushes you to design everything as small , self- contained mini-applications That sounds a bit like the old UNIX principle .
And what 's wrong with having applications that do small things and do it well .
I do n't want a picture application with it 's own twitter functionality , I have a proper twitter client for that .
etc . The biggest reason he gives while this is bad is because it destroys then recreates an activity upon rotating the screen .
What I 've noticed on my droid is that application refresh the screen when the screen is rotated .
To get around the refreshing , developers have to hack around google 's API .</tokentext>
<sentencetext>Point 2.
The Tyranny of the ActivityAndroid, by contrast, pushes you to design everything as small, self- contained mini-applications

That sounds a bit like the old UNIX principle.
And what's wrong with having applications that do small things and do it well.
I don't want a picture application with it's own twitter functionality, I have a proper twitter client for that.
etc.

The biggest reason he gives while this is bad is because it destroys then recreates an activity upon rotating the screen.
What I've noticed on my droid is that application refresh the screen when the screen is rotated.
To get around the refreshing, developers have to hack around google's API.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736420</id>
	<title>Re:dumb article/crappy developer</title>
	<author>fredrik70</author>
	<datestamp>1263308700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually, It's up to the OS, the OS *might* keep it running, until it needs the resources held by the app.<br>See this:<br><a href="http://www.anddev.org/lifecycle\_of\_an\_activity-t81.html" title="anddev.org">http://www.anddev.org/lifecycle\_of\_an\_activity-t81.html</a> [anddev.org]</p></htmltext>
<tokenext>Actually , It 's up to the OS , the OS * might * keep it running , until it needs the resources held by the app.See this : http : //www.anddev.org/lifecycle \ _of \ _an \ _activity-t81.html [ anddev.org ]</tokentext>
<sentencetext>Actually, It's up to the OS, the OS *might* keep it running, until it needs the resources held by the app.See this:http://www.anddev.org/lifecycle\_of\_an\_activity-t81.html [anddev.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736186</id>
	<title>Consider the source</title>
	<author>Anonymous</author>
	<datestamp>1263307080000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>Chris Haseman is an independent software engineer specializing in wireless development. He can be found riding his bike between coffee shops in San Francisco. He's the author of the book Android Essentials (published by Apress). In his spare time, he's a resident DJ at xtcradio.com and a martial arts instructor.</p></div></blockquote><p>Also, I hear he's fluent in Sanskrit and can divide by zero.

</p><p>A smug superficially supercilious fuck-knuckle hates Android?  Well, I guess I'll give it a second look then!  I know which 'essential' book about it to avoid, at least.</p></div>
	</htmltext>
<tokenext>Chris Haseman is an independent software engineer specializing in wireless development .
He can be found riding his bike between coffee shops in San Francisco .
He 's the author of the book Android Essentials ( published by Apress ) .
In his spare time , he 's a resident DJ at xtcradio.com and a martial arts instructor.Also , I hear he 's fluent in Sanskrit and can divide by zero .
A smug superficially supercilious fuck-knuckle hates Android ?
Well , I guess I 'll give it a second look then !
I know which 'essential ' book about it to avoid , at least .</tokentext>
<sentencetext>Chris Haseman is an independent software engineer specializing in wireless development.
He can be found riding his bike between coffee shops in San Francisco.
He's the author of the book Android Essentials (published by Apress).
In his spare time, he's a resident DJ at xtcradio.com and a martial arts instructor.Also, I hear he's fluent in Sanskrit and can divide by zero.
A smug superficially supercilious fuck-knuckle hates Android?
Well, I guess I'll give it a second look then!
I know which 'essential' book about it to avoid, at least.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740312</id>
	<title>What is the opposite of damning with faint praise?</title>
	<author>shoor</author>
	<datestamp>1263323460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>The author seems to be praising Android with faint damnation.</htmltext>
<tokenext>The author seems to be praising Android with faint damnation .</tokentext>
<sentencetext>The author seems to be praising Android with faint damnation.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736350</id>
	<title>Re:Unix way</title>
	<author>fredrik70</author>
	<datestamp>1263308160000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Indeed, the cool thing is that Activities can be shared between processes, My app, for example, can for example make use of Google's picture browsing or the google map activity , no need to write one myself.<br>Activities are placed on a stack, so when the user hits the back button to leave the 3rd party activity they are returned to my activity</p></htmltext>
<tokenext>Indeed , the cool thing is that Activities can be shared between processes , My app , for example , can for example make use of Google 's picture browsing or the google map activity , no need to write one myself.Activities are placed on a stack , so when the user hits the back button to leave the 3rd party activity they are returned to my activity</tokentext>
<sentencetext>Indeed, the cool thing is that Activities can be shared between processes, My app, for example, can for example make use of Google's picture browsing or the google map activity , no need to write one myself.Activities are placed on a stack, so when the user hits the back button to leave the 3rd party activity they are returned to my activity</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162</id>
	<title>veteran mobile application developer ?</title>
	<author>ardiri</author>
	<datestamp>1263306960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>&gt;&gt; how long does it take to be a "veteran mobile application developer?"</p><p>checking out his profile (http://www.linkedin.com/pub/chris-haseman/1/369/a32) he has barely touched the majority of mobile platforms<nobr> <wbr></nobr>:) where is his symbian, palm os (68k, arm), ebookman, embedded linux, psp, nintendo ds, experience? surely - some of us started this stuff professionally back in the late 1990's with devices like the newton and palm professional. boy how things have changed - yet some things stay the same. he announces himself that  ""(and by "in my day," I mean two years ago)"".</p><p>&gt;&gt; 3. Device Debugging</p><p>be thankful - some platforms you still need to do printf() style debugging.</p><p>&gt;&gt; 6. Java&mdash;Thanks, But I'll Take It from Here</p><p>Java - probably the worst language used on mobile devices to date. the desktop and server platform has evolved in many ways which are not being reflected in the mobile space; due to battery life, talk time etc - the typical moore's law of computing doesn't apply to mobile phones. there was a period where CPU speeds dropped on mobile devices - hopefully things will change coming up with new ARM and low powered x86 CPU's - but time will tell.</p><p>A true mobile developer demands a native C/C++ interface on mobile devices - if you want something done, more than a bouncing ball on the screen - its the preferred way. NDK under Android is a must - C/C++ isn't that bad - if you know what you are doing.</p><p>&gt;&gt; 8. Platform Fragmentation</p><p>its a problem? come on - seriously. you deal with it. you design around it; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues. just because most companies hire an outsourcing department or "specialists" on specific platforms isn't a problem - it is a choice. there are plenty of alternatives out there.</p></htmltext>
<tokenext>&gt; &gt; how long does it take to be a " veteran mobile application developer ?
" checking out his profile ( http : //www.linkedin.com/pub/chris-haseman/1/369/a32 ) he has barely touched the majority of mobile platforms : ) where is his symbian , palm os ( 68k , arm ) , ebookman , embedded linux , psp , nintendo ds , experience ?
surely - some of us started this stuff professionally back in the late 1990 's with devices like the newton and palm professional .
boy how things have changed - yet some things stay the same .
he announces himself that " " ( and by " in my day , " I mean two years ago ) " " . &gt; &gt; 3 .
Device Debuggingbe thankful - some platforms you still need to do printf ( ) style debugging. &gt; &gt; 6 .
Java    Thanks , But I 'll Take It from HereJava - probably the worst language used on mobile devices to date .
the desktop and server platform has evolved in many ways which are not being reflected in the mobile space ; due to battery life , talk time etc - the typical moore 's law of computing does n't apply to mobile phones .
there was a period where CPU speeds dropped on mobile devices - hopefully things will change coming up with new ARM and low powered x86 CPU 's - but time will tell.A true mobile developer demands a native C/C + + interface on mobile devices - if you want something done , more than a bouncing ball on the screen - its the preferred way .
NDK under Android is a must - C/C + + is n't that bad - if you know what you are doing. &gt; &gt; 8 .
Platform Fragmentationits a problem ?
come on - seriously .
you deal with it .
you design around it ; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues .
just because most companies hire an outsourcing department or " specialists " on specific platforms is n't a problem - it is a choice .
there are plenty of alternatives out there .</tokentext>
<sentencetext>&gt;&gt; how long does it take to be a "veteran mobile application developer?
"checking out his profile (http://www.linkedin.com/pub/chris-haseman/1/369/a32) he has barely touched the majority of mobile platforms :) where is his symbian, palm os (68k, arm), ebookman, embedded linux, psp, nintendo ds, experience?
surely - some of us started this stuff professionally back in the late 1990's with devices like the newton and palm professional.
boy how things have changed - yet some things stay the same.
he announces himself that  ""(and by "in my day," I mean two years ago)"".&gt;&gt; 3.
Device Debuggingbe thankful - some platforms you still need to do printf() style debugging.&gt;&gt; 6.
Java—Thanks, But I'll Take It from HereJava - probably the worst language used on mobile devices to date.
the desktop and server platform has evolved in many ways which are not being reflected in the mobile space; due to battery life, talk time etc - the typical moore's law of computing doesn't apply to mobile phones.
there was a period where CPU speeds dropped on mobile devices - hopefully things will change coming up with new ARM and low powered x86 CPU's - but time will tell.A true mobile developer demands a native C/C++ interface on mobile devices - if you want something done, more than a bouncing ball on the screen - its the preferred way.
NDK under Android is a must - C/C++ isn't that bad - if you know what you are doing.&gt;&gt; 8.
Platform Fragmentationits a problem?
come on - seriously.
you deal with it.
you design around it; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues.
just because most companies hire an outsourcing department or "specialists" on specific platforms isn't a problem - it is a choice.
there are plenty of alternatives out there.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736234</id>
	<title>Re:dumb article/crappy developer</title>
	<author>dskzero</author>
	<datestamp>1263307380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I don't think you read the article properly. Despite your undying love of google forcing you to accept everything from them (i'm liberally assuming here), there some legitimately complaints. The ammount of mini apps running around go directly against the idea that's been creeping around of making applications run on less files, like Mac application structure, or so i've heard, does, while the running applications it's a very valid point.

The main point to be taken of is the fact that everyone and their mothers will develop handsets with different quirks, which can easily ruin the OS as applications will not "simply work", as they do on Symbian or the Iphone. Either Google sends down the hammer of standards, or the OS is doomed.</htmltext>
<tokenext>I do n't think you read the article properly .
Despite your undying love of google forcing you to accept everything from them ( i 'm liberally assuming here ) , there some legitimately complaints .
The ammount of mini apps running around go directly against the idea that 's been creeping around of making applications run on less files , like Mac application structure , or so i 've heard , does , while the running applications it 's a very valid point .
The main point to be taken of is the fact that everyone and their mothers will develop handsets with different quirks , which can easily ruin the OS as applications will not " simply work " , as they do on Symbian or the Iphone .
Either Google sends down the hammer of standards , or the OS is doomed .</tokentext>
<sentencetext>I don't think you read the article properly.
Despite your undying love of google forcing you to accept everything from them (i'm liberally assuming here), there some legitimately complaints.
The ammount of mini apps running around go directly against the idea that's been creeping around of making applications run on less files, like Mac application structure, or so i've heard, does, while the running applications it's a very valid point.
The main point to be taken of is the fact that everyone and their mothers will develop handsets with different quirks, which can easily ruin the OS as applications will not "simply work", as they do on Symbian or the Iphone.
Either Google sends down the hammer of standards, or the OS is doomed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736306</id>
	<title>Re:What?</title>
	<author>Anonymous</author>
	<datestamp>1263307920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>"You're making it way too easy to use to create applications!"</p></div></blockquote><p>Well, isn't that the point?</p><p>I've developed on Android the last weeks, because I felt the challenges this summer creating apps are mainly "teensoftware", which is great in alot of dimensions (getting people interested in programming, there's alot of progamming work out there, stop making people wan ting to get lobotomies because you "set your job safe" by writing hard to maintain code) but that teensoftware, doesn't scratch my itch.</p><p>Teens and likes don't know the needs of people in the workingforce or businesses and that's where you have your targetaudience if you want to get serious on mobile development. (I know some government projects working on augmented reality software, which is pretty cool. But that's also not where my focus is.)</p><p>Concerning the "ease", it took some thought to get performance right in my applications and generics aren't that easy as in<nobr> <wbr></nobr>.NET. There's some more thought required and the debugger might be nice but<nobr> <wbr></nobr>.NET started to feel like playing with playdoh compared to receiving a bag with sand and a cup of water.</p><p>I wonder what the purpose of IT and development is, is it coming to a solution or is it messing on the way to a solution? I know I get more out of delivering something then maintaining a mess or constantly being "almost done".</p><p>Easy of development is something that you should be happy about, you're a programmer above a procrastinator or even a sadomasochist, right?</p></div>
	</htmltext>
<tokenext>" You 're making it way too easy to use to create applications !
" Well , is n't that the point ? I 've developed on Android the last weeks , because I felt the challenges this summer creating apps are mainly " teensoftware " , which is great in alot of dimensions ( getting people interested in programming , there 's alot of progamming work out there , stop making people wan ting to get lobotomies because you " set your job safe " by writing hard to maintain code ) but that teensoftware , does n't scratch my itch.Teens and likes do n't know the needs of people in the workingforce or businesses and that 's where you have your targetaudience if you want to get serious on mobile development .
( I know some government projects working on augmented reality software , which is pretty cool .
But that 's also not where my focus is .
) Concerning the " ease " , it took some thought to get performance right in my applications and generics are n't that easy as in .NET .
There 's some more thought required and the debugger might be nice but .NET started to feel like playing with playdoh compared to receiving a bag with sand and a cup of water.I wonder what the purpose of IT and development is , is it coming to a solution or is it messing on the way to a solution ?
I know I get more out of delivering something then maintaining a mess or constantly being " almost done " .Easy of development is something that you should be happy about , you 're a programmer above a procrastinator or even a sadomasochist , right ?</tokentext>
<sentencetext>"You're making it way too easy to use to create applications!
"Well, isn't that the point?I've developed on Android the last weeks, because I felt the challenges this summer creating apps are mainly "teensoftware", which is great in alot of dimensions (getting people interested in programming, there's alot of progamming work out there, stop making people wan ting to get lobotomies because you "set your job safe" by writing hard to maintain code) but that teensoftware, doesn't scratch my itch.Teens and likes don't know the needs of people in the workingforce or businesses and that's where you have your targetaudience if you want to get serious on mobile development.
(I know some government projects working on augmented reality software, which is pretty cool.
But that's also not where my focus is.
)Concerning the "ease", it took some thought to get performance right in my applications and generics aren't that easy as in .NET.
There's some more thought required and the debugger might be nice but .NET started to feel like playing with playdoh compared to receiving a bag with sand and a cup of water.I wonder what the purpose of IT and development is, is it coming to a solution or is it messing on the way to a solution?
I know I get more out of delivering something then maintaining a mess or constantly being "almost done".Easy of development is something that you should be happy about, you're a programmer above a procrastinator or even a sadomasochist, right?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</id>
	<title>What?</title>
	<author>Anonymous</author>
	<datestamp>1263305460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Disclaimer: I actually read the FA (yes, I know this is slashdot).

This guy is angry because, amongst other things, Google has made 40\% of his debugging skills useless. Apperantly, his problem is that this means that other people without his "superskills" can develop software for Android.</htmltext>
<tokenext>Disclaimer : I actually read the FA ( yes , I know this is slashdot ) .
This guy is angry because , amongst other things , Google has made 40 \ % of his debugging skills useless .
Apperantly , his problem is that this means that other people without his " superskills " can develop software for Android .</tokentext>
<sentencetext>Disclaimer: I actually read the FA (yes, I know this is slashdot).
This guy is angry because, amongst other things, Google has made 40\% of his debugging skills useless.
Apperantly, his problem is that this means that other people without his "superskills" can develop software for Android.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737788</id>
	<title>Re:What?</title>
	<author>godefroi</author>
	<datestamp>1263314580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>More like, "I hate Android because it's just WAY TOO AWESOME! Buy my Android book!"</p></htmltext>
<tokenext>More like , " I hate Android because it 's just WAY TOO AWESOME !
Buy my Android book !
"</tokentext>
<sentencetext>More like, "I hate Android because it's just WAY TOO AWESOME!
Buy my Android book!
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540</id>
	<title>why Java?</title>
	<author>ShenTheWise</author>
	<datestamp>1263309420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>My single Android complaint: Why, oh why must it be Java based?</p><p>1) Sandboxing in Android actually happens at the Linux process level. Every app run its in own isolated process, with its own instance of the Java VM. You can remove the VM form the picture and it would be just as safe.<br>2) You cannot build once run everywhere. Its a myth. With J2ME phones, devs test and optimize for every supported handset, and it will be the same for Android.<br>3) Java *IS* an order of magnitude slower than C/ASM for many things that are important for games, such as matrix math. Google knows this and is trying to work around it with JNI/NDK, but really why the complication?</p><p>I guess its too late now, but it makes me very, very sad.<br>(And makes Apple very, very happy)</p></htmltext>
<tokenext>My single Android complaint : Why , oh why must it be Java based ? 1 ) Sandboxing in Android actually happens at the Linux process level .
Every app run its in own isolated process , with its own instance of the Java VM .
You can remove the VM form the picture and it would be just as safe.2 ) You can not build once run everywhere .
Its a myth .
With J2ME phones , devs test and optimize for every supported handset , and it will be the same for Android.3 ) Java * IS * an order of magnitude slower than C/ASM for many things that are important for games , such as matrix math .
Google knows this and is trying to work around it with JNI/NDK , but really why the complication ? I guess its too late now , but it makes me very , very sad .
( And makes Apple very , very happy )</tokentext>
<sentencetext>My single Android complaint: Why, oh why must it be Java based?1) Sandboxing in Android actually happens at the Linux process level.
Every app run its in own isolated process, with its own instance of the Java VM.
You can remove the VM form the picture and it would be just as safe.2) You cannot build once run everywhere.
Its a myth.
With J2ME phones, devs test and optimize for every supported handset, and it will be the same for Android.3) Java *IS* an order of magnitude slower than C/ASM for many things that are important for games, such as matrix math.
Google knows this and is trying to work around it with JNI/NDK, but really why the complication?I guess its too late now, but it makes me very, very sad.
(And makes Apple very, very happy)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738720</id>
	<title>Re:What?</title>
	<author>alteran</author>
	<datestamp>1263317760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think it's obvious that specific point was tongue-in-cheek.</p><p>His mix of legitimate gripes and tongue-in-cheek "criticism" makes the article a little tricky to parse-- but I learned some interesting stuff about Android.</p></htmltext>
<tokenext>I think it 's obvious that specific point was tongue-in-cheek.His mix of legitimate gripes and tongue-in-cheek " criticism " makes the article a little tricky to parse-- but I learned some interesting stuff about Android .</tokentext>
<sentencetext>I think it's obvious that specific point was tongue-in-cheek.His mix of legitimate gripes and tongue-in-cheek "criticism" makes the article a little tricky to parse-- but I learned some interesting stuff about Android.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30741342</id>
	<title>Hit and miss, some good points</title>
	<author>Zigurd</author>
	<datestamp>1263327420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The gripes are, unfortunately, mostly off target. But you can't blame a developer for having gripes. They deserve an answer. So here goes:</p><p>1. Open Source</p><p>The heart of this gripe appears to be "What's worse is Google knows how to protect valued code; Its Maps, Gmail, and Store applications aren't open source. Figuring out when it's okay to include one of those in your own application requires a crack legal team with a hotline to the EFF. "</p><p>This is a non-issue. Google hasn't released any proprietary code. Using the capabilities of these applications, or any other FOSS or proprietary applications in Android by means of their remote method interfaces or their Intent filters is OK unless the APIs require a key, as with the maps APIs. The process of getting a Google Maps API key is described here:  <a href="http://code.google.com/apis/maps/signup.html" title="google.com">http://code.google.com/apis/maps/signup.html</a> [google.com] and most introductory Android programming books cover it, too (<a href="http://www.amazon.com/dp/0596521472" title="amazon.com">http://www.amazon.com/dp/0596521472</a> [amazon.com] in chapter 7). J2ME, BREW, and Symbian all require app signing and all support protected APIs.</p><p>2. The Tyranny of the Activity</p><p>Android has a unique programming model. It wasn't designed just to make a coder's life difficult. It was designed to prevent a small-screen UI from becoming a maze of hierarchical screen transition and enable re-use of functionality across applications. Android makes "shoveware" ports look bad, which is what Haseman seems to be griping about.</p><p>3. Device Debugging</p><p>This "gripe" is not really a gripe, but good-natured praise for the ease of debugging on Android.</p><p>4. Applications Never, Ever Quit</p><p>Android has an interesting and powerful application lifecycle. And, since Android is multi-tasking, more developers will notice that their application has a lifecycle.</p><p>5. The Developer Cooperative</p><p>This is a valid gripe: On the one hand, Android can manhandle your application's lifecycle, and on the other hand, it is fairly easy for applications to become battery-eaters. Google's developers could have done a better job of automatically detecting battery vampires. Use the "Battery use" in the "About phone" menu in "Settings" to find the applications and other system functions using the battery. That's a tip taken from this article: <a href="http://answers.oreilly.com/topic/862-ten-tips-for-android-application-development/" title="oreilly.com">http://answers.oreilly.com/topic/862-ten-tips-for-android-application-development/</a> [oreilly.com] </p><p>6.  Java&mdash;Thanks, But I'll Take It from Here</p><p>Haseman says: "While it might speed time to market by freeing us from chasing down heap corruptions and memory leaks (two of my least favorite tasks), it can make it nearly impossible to, say, write an anti-aliased font library that renders in a reasonable amount of time. Sure, a developer can write custom libraries in C with their NDK, but now we're debugging two languages instead of one."</p><p>Java in Android runs on the Dalvik VM, which, up to now, is a pure interpreter: No precompiler, no JIT. It relies completely on the ability to mix in libraries in C via JNIs <a href="http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/jniTOC.html" title="sun.com">http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/jniTOC.html</a> [sun.com] and the NDK <a href="http://developer.android.com/sdk/ndk/1.6\_r1/index.html" title="android.com">http://developer.android.com/sdk/ndk/1.6\_r1/index.html</a> [android.com].</p><p>Why? The short answer is it is hard to put a JIT compiler in a battery powered device. So the developer has to decide what code belongs in Java and what code belongs in C.</p><p>7. "Intents"</p><p>Here I am right with Haseman, since his gripe is having to write (<a href="http://www.amazon.com/Android-Essentials-Firstpress-Chris-Haseman/dp/1430210648/" title="amazon.com">http://www.amazon.com/Android-Essentials-Firstpress-Chris-Haseman/dp/1430210648/</a> [amazon.com]) about classes with names that lend themselves to drifting into being nouns. The Activity, Intent, and Service classes in Android twist up one's prose worse that quarks tha</p></htmltext>
<tokenext>The gripes are , unfortunately , mostly off target .
But you ca n't blame a developer for having gripes .
They deserve an answer .
So here goes : 1 .
Open SourceThe heart of this gripe appears to be " What 's worse is Google knows how to protect valued code ; Its Maps , Gmail , and Store applications are n't open source .
Figuring out when it 's okay to include one of those in your own application requires a crack legal team with a hotline to the EFF .
" This is a non-issue .
Google has n't released any proprietary code .
Using the capabilities of these applications , or any other FOSS or proprietary applications in Android by means of their remote method interfaces or their Intent filters is OK unless the APIs require a key , as with the maps APIs .
The process of getting a Google Maps API key is described here : http : //code.google.com/apis/maps/signup.html [ google.com ] and most introductory Android programming books cover it , too ( http : //www.amazon.com/dp/0596521472 [ amazon.com ] in chapter 7 ) .
J2ME , BREW , and Symbian all require app signing and all support protected APIs.2 .
The Tyranny of the ActivityAndroid has a unique programming model .
It was n't designed just to make a coder 's life difficult .
It was designed to prevent a small-screen UI from becoming a maze of hierarchical screen transition and enable re-use of functionality across applications .
Android makes " shoveware " ports look bad , which is what Haseman seems to be griping about.3 .
Device DebuggingThis " gripe " is not really a gripe , but good-natured praise for the ease of debugging on Android.4 .
Applications Never , Ever QuitAndroid has an interesting and powerful application lifecycle .
And , since Android is multi-tasking , more developers will notice that their application has a lifecycle.5 .
The Developer CooperativeThis is a valid gripe : On the one hand , Android can manhandle your application 's lifecycle , and on the other hand , it is fairly easy for applications to become battery-eaters .
Google 's developers could have done a better job of automatically detecting battery vampires .
Use the " Battery use " in the " About phone " menu in " Settings " to find the applications and other system functions using the battery .
That 's a tip taken from this article : http : //answers.oreilly.com/topic/862-ten-tips-for-android-application-development/ [ oreilly.com ] 6 .
Java    Thanks , But I 'll Take It from HereHaseman says : " While it might speed time to market by freeing us from chasing down heap corruptions and memory leaks ( two of my least favorite tasks ) , it can make it nearly impossible to , say , write an anti-aliased font library that renders in a reasonable amount of time .
Sure , a developer can write custom libraries in C with their NDK , but now we 're debugging two languages instead of one .
" Java in Android runs on the Dalvik VM , which , up to now , is a pure interpreter : No precompiler , no JIT .
It relies completely on the ability to mix in libraries in C via JNIs http : //java.sun.com/j2se/1.5.0/docs/guide/jni/spec/jniTOC.html [ sun.com ] and the NDK http : //developer.android.com/sdk/ndk/1.6 \ _r1/index.html [ android.com ] .Why ?
The short answer is it is hard to put a JIT compiler in a battery powered device .
So the developer has to decide what code belongs in Java and what code belongs in C.7 .
" Intents " Here I am right with Haseman , since his gripe is having to write ( http : //www.amazon.com/Android-Essentials-Firstpress-Chris-Haseman/dp/1430210648/ [ amazon.com ] ) about classes with names that lend themselves to drifting into being nouns .
The Activity , Intent , and Service classes in Android twist up one 's prose worse that quarks tha</tokentext>
<sentencetext>The gripes are, unfortunately, mostly off target.
But you can't blame a developer for having gripes.
They deserve an answer.
So here goes:1.
Open SourceThe heart of this gripe appears to be "What's worse is Google knows how to protect valued code; Its Maps, Gmail, and Store applications aren't open source.
Figuring out when it's okay to include one of those in your own application requires a crack legal team with a hotline to the EFF.
"This is a non-issue.
Google hasn't released any proprietary code.
Using the capabilities of these applications, or any other FOSS or proprietary applications in Android by means of their remote method interfaces or their Intent filters is OK unless the APIs require a key, as with the maps APIs.
The process of getting a Google Maps API key is described here:  http://code.google.com/apis/maps/signup.html [google.com] and most introductory Android programming books cover it, too (http://www.amazon.com/dp/0596521472 [amazon.com] in chapter 7).
J2ME, BREW, and Symbian all require app signing and all support protected APIs.2.
The Tyranny of the ActivityAndroid has a unique programming model.
It wasn't designed just to make a coder's life difficult.
It was designed to prevent a small-screen UI from becoming a maze of hierarchical screen transition and enable re-use of functionality across applications.
Android makes "shoveware" ports look bad, which is what Haseman seems to be griping about.3.
Device DebuggingThis "gripe" is not really a gripe, but good-natured praise for the ease of debugging on Android.4.
Applications Never, Ever QuitAndroid has an interesting and powerful application lifecycle.
And, since Android is multi-tasking, more developers will notice that their application has a lifecycle.5.
The Developer CooperativeThis is a valid gripe: On the one hand, Android can manhandle your application's lifecycle, and on the other hand, it is fairly easy for applications to become battery-eaters.
Google's developers could have done a better job of automatically detecting battery vampires.
Use the "Battery use" in the "About phone" menu in "Settings" to find the applications and other system functions using the battery.
That's a tip taken from this article: http://answers.oreilly.com/topic/862-ten-tips-for-android-application-development/ [oreilly.com] 6.
Java—Thanks, But I'll Take It from HereHaseman says: "While it might speed time to market by freeing us from chasing down heap corruptions and memory leaks (two of my least favorite tasks), it can make it nearly impossible to, say, write an anti-aliased font library that renders in a reasonable amount of time.
Sure, a developer can write custom libraries in C with their NDK, but now we're debugging two languages instead of one.
"Java in Android runs on the Dalvik VM, which, up to now, is a pure interpreter: No precompiler, no JIT.
It relies completely on the ability to mix in libraries in C via JNIs http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/jniTOC.html [sun.com] and the NDK http://developer.android.com/sdk/ndk/1.6\_r1/index.html [android.com].Why?
The short answer is it is hard to put a JIT compiler in a battery powered device.
So the developer has to decide what code belongs in Java and what code belongs in C.7.
"Intents"Here I am right with Haseman, since his gripe is having to write (http://www.amazon.com/Android-Essentials-Firstpress-Chris-Haseman/dp/1430210648/ [amazon.com]) about classes with names that lend themselves to drifting into being nouns.
The Activity, Intent, and Service classes in Android twist up one's prose worse that quarks tha</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740534</id>
	<title>Re:dumb article/crappy developer</title>
	<author>esarjeant</author>
	<datestamp>1263324180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Coming primarily from BlackBerry development, I think this "platform fragmentation" is going to be a real challenge. While the general application architecture is neat, if the device hardware is tweaked for different devices this is going to make it increasingly difficult to develop for.</p><p>Until the BlackBerry JDE included pre-compiler directives, it was a nightmare to support different device hardware. To make matters worse, some hardware API calls (eg: GPS unit) were disabled by certain carriers even if the device supported it. Of course, the advent of the BB Storm brought a whole new world of hurt with a rotating screen not to mention all the new calls you needed to make for the keyboard to appear / disappear whenever needed.</p><p>Since nothing is backward compatible, a BB app compiled for the Storm with JDE 4.7 won't run on a 4.6 device. So the result? You end up with a different JAD file for each operating system version. Don't even get me started on having to sign your apps for the privilege of using "protected" system API calls. Everything runs fine until you get the program onto a real device where the privileged calls are rejected by the BB os and of course the universe of signed API calls changed from release to release as well.</p><p>Google may already be on the road to this El Dorado, I think they are going to need to define a reference platform that all Android powered devices must support. If they don't tackle this now, manufacturers will create variants on the core phone concept and the application marketplace will begin to fracture. The idea that you can build a Midlet and bring it from one device to another hasn't been successful, the display metrics of these phones are too varying and the capabilities of the hardware are diverse -- establish a minimal platform requirement for your applications (ala: iPhone) and this problem goes away.</p></htmltext>
<tokenext>Coming primarily from BlackBerry development , I think this " platform fragmentation " is going to be a real challenge .
While the general application architecture is neat , if the device hardware is tweaked for different devices this is going to make it increasingly difficult to develop for.Until the BlackBerry JDE included pre-compiler directives , it was a nightmare to support different device hardware .
To make matters worse , some hardware API calls ( eg : GPS unit ) were disabled by certain carriers even if the device supported it .
Of course , the advent of the BB Storm brought a whole new world of hurt with a rotating screen not to mention all the new calls you needed to make for the keyboard to appear / disappear whenever needed.Since nothing is backward compatible , a BB app compiled for the Storm with JDE 4.7 wo n't run on a 4.6 device .
So the result ?
You end up with a different JAD file for each operating system version .
Do n't even get me started on having to sign your apps for the privilege of using " protected " system API calls .
Everything runs fine until you get the program onto a real device where the privileged calls are rejected by the BB os and of course the universe of signed API calls changed from release to release as well.Google may already be on the road to this El Dorado , I think they are going to need to define a reference platform that all Android powered devices must support .
If they do n't tackle this now , manufacturers will create variants on the core phone concept and the application marketplace will begin to fracture .
The idea that you can build a Midlet and bring it from one device to another has n't been successful , the display metrics of these phones are too varying and the capabilities of the hardware are diverse -- establish a minimal platform requirement for your applications ( ala : iPhone ) and this problem goes away .</tokentext>
<sentencetext>Coming primarily from BlackBerry development, I think this "platform fragmentation" is going to be a real challenge.
While the general application architecture is neat, if the device hardware is tweaked for different devices this is going to make it increasingly difficult to develop for.Until the BlackBerry JDE included pre-compiler directives, it was a nightmare to support different device hardware.
To make matters worse, some hardware API calls (eg: GPS unit) were disabled by certain carriers even if the device supported it.
Of course, the advent of the BB Storm brought a whole new world of hurt with a rotating screen not to mention all the new calls you needed to make for the keyboard to appear / disappear whenever needed.Since nothing is backward compatible, a BB app compiled for the Storm with JDE 4.7 won't run on a 4.6 device.
So the result?
You end up with a different JAD file for each operating system version.
Don't even get me started on having to sign your apps for the privilege of using "protected" system API calls.
Everything runs fine until you get the program onto a real device where the privileged calls are rejected by the BB os and of course the universe of signed API calls changed from release to release as well.Google may already be on the road to this El Dorado, I think they are going to need to define a reference platform that all Android powered devices must support.
If they don't tackle this now, manufacturers will create variants on the core phone concept and the application marketplace will begin to fracture.
The idea that you can build a Midlet and bring it from one device to another hasn't been successful, the display metrics of these phones are too varying and the capabilities of the hardware are diverse -- establish a minimal platform requirement for your applications (ala: iPhone) and this problem goes away.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736234</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736784</id>
	<title>Lack of support for wi-fi proxy</title>
	<author>Anonymous</author>
	<datestamp>1263310560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I don't understand why this doesn't get more attention, or even some basic acknowledgment from the Android team. Lack of a wi-fi proxy means that Android devices are basically useless for corporate/school wi-fi networks.</p><p>When I connect my iPod touch to the corporate wi-fi, I can access the web.  When I connect my Hero to corporate wi-fi, I cannot.  This is a defect.</p></htmltext>
<tokenext>I do n't understand why this does n't get more attention , or even some basic acknowledgment from the Android team .
Lack of a wi-fi proxy means that Android devices are basically useless for corporate/school wi-fi networks.When I connect my iPod touch to the corporate wi-fi , I can access the web .
When I connect my Hero to corporate wi-fi , I can not .
This is a defect .</tokentext>
<sentencetext>I don't understand why this doesn't get more attention, or even some basic acknowledgment from the Android team.
Lack of a wi-fi proxy means that Android devices are basically useless for corporate/school wi-fi networks.When I connect my iPod touch to the corporate wi-fi, I can access the web.
When I connect my Hero to corporate wi-fi, I cannot.
This is a defect.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026</id>
	<title>dumb article/crappy developer</title>
	<author>Anonymous</author>
	<datestamp>1263306240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Point 1. Open Source<br>As the submitter also pointed out. I don't see any problem with the Apache Software License 2.0 licensed Open Source code of Android. How is that a developer gripe? APL2 allows you to close whatever you want to keep closed.</p><blockquote><div><p>Figuring out when it's okay to include one of those in your own application requires a crack legal team with a hotline to the EFF.</p></div></blockquote><p>Actually, that's quite simple. It's ok when Google (the copyright holder) says it's ok, otherwise it's not.</p><p>Point 2. The Tyranny of the Activity</p><blockquote><div><p>Android, by contrast, pushes you to design everything as small, self-contained mini-applications.</p></div></blockquote><p>That sounds a bit like the old UNIX principle. And what's wrong with having applications that do small things and do it well. I don't want a picture application with it's own twitter functionality, I have a proper twitter client for that. etc.</p><p>Point 3. Device Debugging</p><blockquote><div><p>Why do I hate this extremely useful tool? I hate it because it makes about 40\% of my debugging skills nearly useless!</p></div></blockquote><p>Ok.. so... this article is an humor piece instead of a real article/rant? Or is the writer simply a moron?</p><p>Point 4. Applications Never, Ever Quit</p><blockquote><div><p>but your icon stays in the list of running tasks</p></div></blockquote><p>Maybe this is a new feature in Android 2.x. But the list of applications you get when holding down the home button is not "running applications" but simply a list of recently started applications. When I leave an application and it has no active processes then it won't show up in the process list. So, I'm quite sure it's not running.</p><p>Point 5. The Developer Cooperative<br>Yes, it would be very nice if the end-user could define system resource limits for individual applications. But other than that, I don't want artificial limitations enforced by the OS by default. Some application simply need more resources than others. If an application is crap, I will uninstall it. Just like I do on my normal PCs.</p><p>You know what... I'm not even interesting in the other 5 points on the second page.</p></div>
	</htmltext>
<tokenext>Point 1 .
Open SourceAs the submitter also pointed out .
I do n't see any problem with the Apache Software License 2.0 licensed Open Source code of Android .
How is that a developer gripe ?
APL2 allows you to close whatever you want to keep closed.Figuring out when it 's okay to include one of those in your own application requires a crack legal team with a hotline to the EFF.Actually , that 's quite simple .
It 's ok when Google ( the copyright holder ) says it 's ok , otherwise it 's not.Point 2 .
The Tyranny of the ActivityAndroid , by contrast , pushes you to design everything as small , self-contained mini-applications.That sounds a bit like the old UNIX principle .
And what 's wrong with having applications that do small things and do it well .
I do n't want a picture application with it 's own twitter functionality , I have a proper twitter client for that .
etc.Point 3 .
Device DebuggingWhy do I hate this extremely useful tool ?
I hate it because it makes about 40 \ % of my debugging skills nearly useless ! Ok.. so... this article is an humor piece instead of a real article/rant ?
Or is the writer simply a moron ? Point 4 .
Applications Never , Ever Quitbut your icon stays in the list of running tasksMaybe this is a new feature in Android 2.x .
But the list of applications you get when holding down the home button is not " running applications " but simply a list of recently started applications .
When I leave an application and it has no active processes then it wo n't show up in the process list .
So , I 'm quite sure it 's not running.Point 5 .
The Developer CooperativeYes , it would be very nice if the end-user could define system resource limits for individual applications .
But other than that , I do n't want artificial limitations enforced by the OS by default .
Some application simply need more resources than others .
If an application is crap , I will uninstall it .
Just like I do on my normal PCs.You know what... I 'm not even interesting in the other 5 points on the second page .</tokentext>
<sentencetext>Point 1.
Open SourceAs the submitter also pointed out.
I don't see any problem with the Apache Software License 2.0 licensed Open Source code of Android.
How is that a developer gripe?
APL2 allows you to close whatever you want to keep closed.Figuring out when it's okay to include one of those in your own application requires a crack legal team with a hotline to the EFF.Actually, that's quite simple.
It's ok when Google (the copyright holder) says it's ok, otherwise it's not.Point 2.
The Tyranny of the ActivityAndroid, by contrast, pushes you to design everything as small, self-contained mini-applications.That sounds a bit like the old UNIX principle.
And what's wrong with having applications that do small things and do it well.
I don't want a picture application with it's own twitter functionality, I have a proper twitter client for that.
etc.Point 3.
Device DebuggingWhy do I hate this extremely useful tool?
I hate it because it makes about 40\% of my debugging skills nearly useless!Ok.. so... this article is an humor piece instead of a real article/rant?
Or is the writer simply a moron?Point 4.
Applications Never, Ever Quitbut your icon stays in the list of running tasksMaybe this is a new feature in Android 2.x.
But the list of applications you get when holding down the home button is not "running applications" but simply a list of recently started applications.
When I leave an application and it has no active processes then it won't show up in the process list.
So, I'm quite sure it's not running.Point 5.
The Developer CooperativeYes, it would be very nice if the end-user could define system resource limits for individual applications.
But other than that, I don't want artificial limitations enforced by the OS by default.
Some application simply need more resources than others.
If an application is crap, I will uninstall it.
Just like I do on my normal PCs.You know what... I'm not even interesting in the other 5 points on the second page.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930</id>
	<title>Unix way</title>
	<author>Nikademus</author>
	<datestamp>1263305580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>"Android, by contrast, pushes you to design everything as small, self-contained mini-applications."</p><p>Hey, that's called the Unix way.</p></htmltext>
<tokenext>" Android , by contrast , pushes you to design everything as small , self-contained mini-applications .
" Hey , that 's called the Unix way .</tokentext>
<sentencetext>"Android, by contrast, pushes you to design everything as small, self-contained mini-applications.
"Hey, that's called the Unix way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737796</id>
	<title>Re:And still ...</title>
	<author>SQLGuru</author>
	<datestamp>1263314640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'd actually like to see some Android development done in Go.  I see it as a good direction for both Google and the Platform.</p></htmltext>
<tokenext>I 'd actually like to see some Android development done in Go .
I see it as a good direction for both Google and the Platform .</tokentext>
<sentencetext>I'd actually like to see some Android development done in Go.
I see it as a good direction for both Google and the Platform.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735934</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746154</id>
	<title>Re:And still ...</title>
	<author>Anonymous</author>
	<datestamp>1263309480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Call it an "Intention". You either have or haven't an intent. You can have one or more intentions.</p></htmltext>
<tokenext>Call it an " Intention " .
You either have or have n't an intent .
You can have one or more intentions .</tokentext>
<sentencetext>Call it an "Intention".
You either have or haven't an intent.
You can have one or more intentions.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735934</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736612</id>
	<title>Re:Consider the source</title>
	<author>mcgrew</author>
	<datestamp>1263309780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Also, I hear he's fluent in Sanskrit and can divide by zero.</i></p><p>I can divide by zero. The answer will be incorrect, though.</p></htmltext>
<tokenext>Also , I hear he 's fluent in Sanskrit and can divide by zero.I can divide by zero .
The answer will be incorrect , though .</tokentext>
<sentencetext>Also, I hear he's fluent in Sanskrit and can divide by zero.I can divide by zero.
The answer will be incorrect, though.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736186</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737014</id>
	<title>Re:dumb article/crappy developer</title>
	<author>MikeBabcock</author>
	<datestamp>1263311460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You go play with your 'hammer of standards' platform and I'll stick to the everything just works phone with lots of small working packages that interoperate and we'll see who's got more options next year.</p></htmltext>
<tokenext>You go play with your 'hammer of standards ' platform and I 'll stick to the everything just works phone with lots of small working packages that interoperate and we 'll see who 's got more options next year .</tokentext>
<sentencetext>You go play with your 'hammer of standards' platform and I'll stick to the everything just works phone with lots of small working packages that interoperate and we'll see who's got more options next year.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736234</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737266</id>
	<title>Re:dumb article/crappy developer</title>
	<author>GooberToo</author>
	<datestamp>1263312360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Fire up something like advanced task killer and see what your memory utilization is like. He has a point, getting an app to "close" in the sense that it's not running and not hogging memory is a problem with Android.</p></div><p>The entire point of applications like Advanced Task Killer is to free up memory. But it entirely defeats the purpose as it is itself an application consuming memory. Plus, the application kills battery power like its going out of style because it constantly polls to obtain process lists and per process information. Add in the fact that many users break applications by using it means that most developers absolutely hate the application because it generates bugs reports wasting endless developer time.</p><p>That specific application has widely been dubbed, "Advanced Battery Killer." Who would think that an application constantly polling in the background, consuming CPU, and using scarce memory would be an absolutely waste...lol...</p><p>Thankfully many savvy users are finally realizing that the task killer applications are as much a waste of battery life as they are a waste of dollars. In short, these types of applications prey on the ignorance of the masses and are completely counter productive while being the bane of other developers.</p></div>
	</htmltext>
<tokenext>Fire up something like advanced task killer and see what your memory utilization is like .
He has a point , getting an app to " close " in the sense that it 's not running and not hogging memory is a problem with Android.The entire point of applications like Advanced Task Killer is to free up memory .
But it entirely defeats the purpose as it is itself an application consuming memory .
Plus , the application kills battery power like its going out of style because it constantly polls to obtain process lists and per process information .
Add in the fact that many users break applications by using it means that most developers absolutely hate the application because it generates bugs reports wasting endless developer time.That specific application has widely been dubbed , " Advanced Battery Killer .
" Who would think that an application constantly polling in the background , consuming CPU , and using scarce memory would be an absolutely waste...lol...Thankfully many savvy users are finally realizing that the task killer applications are as much a waste of battery life as they are a waste of dollars .
In short , these types of applications prey on the ignorance of the masses and are completely counter productive while being the bane of other developers .</tokentext>
<sentencetext>Fire up something like advanced task killer and see what your memory utilization is like.
He has a point, getting an app to "close" in the sense that it's not running and not hogging memory is a problem with Android.The entire point of applications like Advanced Task Killer is to free up memory.
But it entirely defeats the purpose as it is itself an application consuming memory.
Plus, the application kills battery power like its going out of style because it constantly polls to obtain process lists and per process information.
Add in the fact that many users break applications by using it means that most developers absolutely hate the application because it generates bugs reports wasting endless developer time.That specific application has widely been dubbed, "Advanced Battery Killer.
" Who would think that an application constantly polling in the background, consuming CPU, and using scarce memory would be an absolutely waste...lol...Thankfully many savvy users are finally realizing that the task killer applications are as much a waste of battery life as they are a waste of dollars.
In short, these types of applications prey on the ignorance of the masses and are completely counter productive while being the bane of other developers.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737076</id>
	<title>Re:What?</title>
	<author>Ash Vince</author>
	<datestamp>1263311640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Disclaimer: I actually read the FA (yes, I know this is slashdot). This guy is angry because, amongst other things, Google has made 40\% of his debugging skills useless. Apperantly, his problem is that this means that other people without his "superskills" can develop software for Android.</p></div><p>I don't think much of his article should be taken seriously. He makes some very valid points but most of it is written to be very tongue in cheek. In other words, he does not really sound very angry. He even mentions at the end of the article that Android is one of his favourite platforms to develop for.</p></div>
	</htmltext>
<tokenext>Disclaimer : I actually read the FA ( yes , I know this is slashdot ) .
This guy is angry because , amongst other things , Google has made 40 \ % of his debugging skills useless .
Apperantly , his problem is that this means that other people without his " superskills " can develop software for Android.I do n't think much of his article should be taken seriously .
He makes some very valid points but most of it is written to be very tongue in cheek .
In other words , he does not really sound very angry .
He even mentions at the end of the article that Android is one of his favourite platforms to develop for .</tokentext>
<sentencetext>Disclaimer: I actually read the FA (yes, I know this is slashdot).
This guy is angry because, amongst other things, Google has made 40\% of his debugging skills useless.
Apperantly, his problem is that this means that other people without his "superskills" can develop software for Android.I don't think much of his article should be taken seriously.
He makes some very valid points but most of it is written to be very tongue in cheek.
In other words, he does not really sound very angry.
He even mentions at the end of the article that Android is one of his favourite platforms to develop for.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736124</id>
	<title>Re:What?</title>
	<author>mcgrew</author>
	<datestamp>1263306780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>1. Open Source. Leave it to Google to place all the code for their handset platform in the hands of the masses</i></p><p>More evidence that opensource=fewerbugs? The statement I quoted suggests the guy is an elitist. I'm not going to RTFA as it'll probably piss me off. No wonder Microsoft hates open source so much. Is this guy primarily an MS dev?</p></htmltext>
<tokenext>1 .
Open Source .
Leave it to Google to place all the code for their handset platform in the hands of the massesMore evidence that opensource = fewerbugs ?
The statement I quoted suggests the guy is an elitist .
I 'm not going to RTFA as it 'll probably piss me off .
No wonder Microsoft hates open source so much .
Is this guy primarily an MS dev ?</tokentext>
<sentencetext>1.
Open Source.
Leave it to Google to place all the code for their handset platform in the hands of the massesMore evidence that opensource=fewerbugs?
The statement I quoted suggests the guy is an elitist.
I'm not going to RTFA as it'll probably piss me off.
No wonder Microsoft hates open source so much.
Is this guy primarily an MS dev?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739652</id>
	<title>Re:What?</title>
	<author>uberjack</author>
	<datestamp>1263320940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>He does have some valid complaints though, specifically #6 (so \_why\_ can't I write an entire app in C?), #3 (Android's management of running apps is still a mystery to me), #8 (I've received complaints that my app's icons look low-res on Droid, and not having one, there's not much I can do short of buying a new phone for testing) and partly #5. With regard to #5, however, you can easily weed out poorly written applications within a day's use of them - for example, I uninstalled Google Listen after two days of use, as I noticed that it cut my battery life by 50\%.

I don't agree with him that Android needs to follow the same design paradigm as other platforms, but I may be biased, as I never developed for any other mobile platform. As odd as Intents and Activities seem, the end result is not a bad one at all, and is even fairly intuitive in many ways (my favorite analogy is Intent==POST request and Activity==web page).</htmltext>
<tokenext>He does have some valid complaints though , specifically # 6 ( so \ _why \ _ ca n't I write an entire app in C ?
) , # 3 ( Android 's management of running apps is still a mystery to me ) , # 8 ( I 've received complaints that my app 's icons look low-res on Droid , and not having one , there 's not much I can do short of buying a new phone for testing ) and partly # 5 .
With regard to # 5 , however , you can easily weed out poorly written applications within a day 's use of them - for example , I uninstalled Google Listen after two days of use , as I noticed that it cut my battery life by 50 \ % .
I do n't agree with him that Android needs to follow the same design paradigm as other platforms , but I may be biased , as I never developed for any other mobile platform .
As odd as Intents and Activities seem , the end result is not a bad one at all , and is even fairly intuitive in many ways ( my favorite analogy is Intent = = POST request and Activity = = web page ) .</tokentext>
<sentencetext>He does have some valid complaints though, specifically #6 (so \_why\_ can't I write an entire app in C?
), #3 (Android's management of running apps is still a mystery to me), #8 (I've received complaints that my app's icons look low-res on Droid, and not having one, there's not much I can do short of buying a new phone for testing) and partly #5.
With regard to #5, however, you can easily weed out poorly written applications within a day's use of them - for example, I uninstalled Google Listen after two days of use, as I noticed that it cut my battery life by 50\%.
I don't agree with him that Android needs to follow the same design paradigm as other platforms, but I may be biased, as I never developed for any other mobile platform.
As odd as Intents and Activities seem, the end result is not a bad one at all, and is even fairly intuitive in many ways (my favorite analogy is Intent==POST request and Activity==web page).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736320</id>
	<title>I'm not a coder however...</title>
	<author>AbRASiON</author>
	<datestamp>1263307980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My comment is probably not worth too much not being a developer at all but I am an iphone owner and I must be honest the Nexus one does look pretty interesting.<br>I'm also an Aussie and the Nexus one isn't coming here unfortunately due to incompatibilities with Telstra (the most evil company around, sadly they do have a good phone network)</p><p>I will say most of his stuff is meaningless to me but as a hardware junkie, his 8'th point about the amount of target platforms, inherant in the nature of an open platform like android is a bit of a concern.<br>There's always positives and negatives in open and closed systems and this is a pretty distinct point, the question is though, what's the solution and who is going to get on it fast?</p><p>I'd like to see it solved because I do quite like my iphone but sadly I finally cracked the shits with it being so locked down and jailbroke it. It's better now but I<nobr> <wbr></nobr>/shouldn't have to/<nobr> <wbr></nobr>.... would like to see an open platform at least be 1/2 as popular as the iphone.</p><p>We'll see I guess..</p></htmltext>
<tokenext>My comment is probably not worth too much not being a developer at all but I am an iphone owner and I must be honest the Nexus one does look pretty interesting.I 'm also an Aussie and the Nexus one is n't coming here unfortunately due to incompatibilities with Telstra ( the most evil company around , sadly they do have a good phone network ) I will say most of his stuff is meaningless to me but as a hardware junkie , his 8'th point about the amount of target platforms , inherant in the nature of an open platform like android is a bit of a concern.There 's always positives and negatives in open and closed systems and this is a pretty distinct point , the question is though , what 's the solution and who is going to get on it fast ? I 'd like to see it solved because I do quite like my iphone but sadly I finally cracked the shits with it being so locked down and jailbroke it .
It 's better now but I /should n't have to/ .... would like to see an open platform at least be 1/2 as popular as the iphone.We 'll see I guess. .</tokentext>
<sentencetext>My comment is probably not worth too much not being a developer at all but I am an iphone owner and I must be honest the Nexus one does look pretty interesting.I'm also an Aussie and the Nexus one isn't coming here unfortunately due to incompatibilities with Telstra (the most evil company around, sadly they do have a good phone network)I will say most of his stuff is meaningless to me but as a hardware junkie, his 8'th point about the amount of target platforms, inherant in the nature of an open platform like android is a bit of a concern.There's always positives and negatives in open and closed systems and this is a pretty distinct point, the question is though, what's the solution and who is going to get on it fast?I'd like to see it solved because I do quite like my iphone but sadly I finally cracked the shits with it being so locked down and jailbroke it.
It's better now but I /shouldn't have to/ .... would like to see an open platform at least be 1/2 as popular as the iphone.We'll see I guess..</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394</id>
	<title>Re:dumb article/crappy developer</title>
	<author>Anonymous</author>
	<datestamp>1263308460000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><i><br>Maybe this is a new feature in Android 2.x. But the list of applications you get when holding down the home button is not "running applications" but simply a list of recently started applications. When I leave an application and it has no active processes then it won't show up in the process list. So, I'm quite sure it's not running.</i></p><p>Fire up something like advanced task killer and see what your memory utilization is like. He has a point, getting an app to "close" in the sense that it's not running and not hogging memory is a problem with Android.</p></htmltext>
<tokenext>Maybe this is a new feature in Android 2.x .
But the list of applications you get when holding down the home button is not " running applications " but simply a list of recently started applications .
When I leave an application and it has no active processes then it wo n't show up in the process list .
So , I 'm quite sure it 's not running.Fire up something like advanced task killer and see what your memory utilization is like .
He has a point , getting an app to " close " in the sense that it 's not running and not hogging memory is a problem with Android .</tokentext>
<sentencetext>Maybe this is a new feature in Android 2.x.
But the list of applications you get when holding down the home button is not "running applications" but simply a list of recently started applications.
When I leave an application and it has no active processes then it won't show up in the process list.
So, I'm quite sure it's not running.Fire up something like advanced task killer and see what your memory utilization is like.
He has a point, getting an app to "close" in the sense that it's not running and not hogging memory is a problem with Android.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740046</id>
	<title>Re:5. Developer Cooperative</title>
	<author>cynyr</author>
	<datestamp>1263322380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>have you thought about not storing the image as an image, but rather just create it on the fly? I remember a while back someone wrote a FPS where all the graphics and textures were generated on the fly.</htmltext>
<tokenext>have you thought about not storing the image as an image , but rather just create it on the fly ?
I remember a while back someone wrote a FPS where all the graphics and textures were generated on the fly .</tokentext>
<sentencetext>have you thought about not storing the image as an image, but rather just create it on the fly?
I remember a while back someone wrote a FPS where all the graphics and textures were generated on the fly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736614</id>
	<title>Re:Unix way</title>
	<author>Goaway</author>
	<datestamp>1263309780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And look how popular that is. Hardly anybody adheres to it, even on Unix itself.</p></htmltext>
<tokenext>And look how popular that is .
Hardly anybody adheres to it , even on Unix itself .</tokentext>
<sentencetext>And look how popular that is.
Hardly anybody adheres to it, even on Unix itself.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736814</id>
	<title>Re:veteran mobile application developer ?</title>
	<author>e2d2</author>
	<datestamp>1263310680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Show us on the doll where Chris Haseman touched you.</p></htmltext>
<tokenext>Show us on the doll where Chris Haseman touched you .</tokentext>
<sentencetext>Show us on the doll where Chris Haseman touched you.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739176</id>
	<title>Re:Unix way</title>
	<author>siride</author>
	<datestamp>1263319200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Linux distros could solve a lot of the dependency problems by simply allowing multiple versions of the same package to be installed side-by-side and including a much larger set of libraries in the default install, which 3rd parties could depend on.  Distros might include several different version of glibc, qt, whatever and then app vendors can assume that unless they are using a very old version, their app can install on any distro and just work without requiring a bunch of dependencies to be newly installed as well.</htmltext>
<tokenext>Linux distros could solve a lot of the dependency problems by simply allowing multiple versions of the same package to be installed side-by-side and including a much larger set of libraries in the default install , which 3rd parties could depend on .
Distros might include several different version of glibc , qt , whatever and then app vendors can assume that unless they are using a very old version , their app can install on any distro and just work without requiring a bunch of dependencies to be newly installed as well .</tokentext>
<sentencetext>Linux distros could solve a lot of the dependency problems by simply allowing multiple versions of the same package to be installed side-by-side and including a much larger set of libraries in the default install, which 3rd parties could depend on.
Distros might include several different version of glibc, qt, whatever and then app vendors can assume that unless they are using a very old version, their app can install on any distro and just work without requiring a bunch of dependencies to be newly installed as well.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736636</id>
	<title>Re:Unix way</title>
	<author>entrigant</author>
	<datestamp>1263309840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Everything you just described has been available in a myriad of forms on several distributions for years. The<nobr> <wbr></nobr>.app bundle might as well be a rpm, details like where the installed files go are just details with good package management.</p><p>Also, any decent distribution will setup mime types so that a click on a package on a website will bring up the installer. Some have taken it further than that, e.g. OpenSUSE with their 1 click installs from their build service. Search. Click. Done.</p></htmltext>
<tokenext>Everything you just described has been available in a myriad of forms on several distributions for years .
The .app bundle might as well be a rpm , details like where the installed files go are just details with good package management.Also , any decent distribution will setup mime types so that a click on a package on a website will bring up the installer .
Some have taken it further than that , e.g .
OpenSUSE with their 1 click installs from their build service .
Search. Click .
Done .</tokentext>
<sentencetext>Everything you just described has been available in a myriad of forms on several distributions for years.
The .app bundle might as well be a rpm, details like where the installed files go are just details with good package management.Also, any decent distribution will setup mime types so that a click on a package on a website will bring up the installer.
Some have taken it further than that, e.g.
OpenSUSE with their 1 click installs from their build service.
Search. Click.
Done.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740654</id>
	<title>Re:dumb article/crappy developer</title>
	<author>Anonymous</author>
	<datestamp>1263324660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So just kill the task killer when you're done with it!</p></htmltext>
<tokenext>So just kill the task killer when you 're done with it !</tokentext>
<sentencetext>So just kill the task killer when you're done with it!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737266</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739680</id>
	<title>I can see his issue</title>
	<author>Anonymous</author>
	<datestamp>1263321060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>2. The Tyranny of the Activity<br>6. Java&mdash;Thanks, But I'll Take It from Here<br>7. "Intents"</p><p>Sounds to me like he's just not comfortable with Java OO development.</p><p>This (fully Java based API on top of POSIX kenel) is the future. This is where Linux desktop should be. The reason for the sad state of the Linux desktop is that C API make it too difficult to create applications more complex trivial. At this point the choice is between<nobr> <wbr></nobr>.NET and Java. Of course Google choose Java.</p><p>I have been looking at the API and the architecture of Android and I am very impressed. It looks very UNIX'ish in many areas. Just consider how they deal with "process groups". It's like POSIX process groups taken to GUI applications level.</p></htmltext>
<tokenext>2 .
The Tyranny of the Activity6 .
Java    Thanks , But I 'll Take It from Here7 .
" Intents " Sounds to me like he 's just not comfortable with Java OO development.This ( fully Java based API on top of POSIX kenel ) is the future .
This is where Linux desktop should be .
The reason for the sad state of the Linux desktop is that C API make it too difficult to create applications more complex trivial .
At this point the choice is between .NET and Java .
Of course Google choose Java.I have been looking at the API and the architecture of Android and I am very impressed .
It looks very UNIX'ish in many areas .
Just consider how they deal with " process groups " .
It 's like POSIX process groups taken to GUI applications level .</tokentext>
<sentencetext>2.
The Tyranny of the Activity6.
Java—Thanks, But I'll Take It from Here7.
"Intents"Sounds to me like he's just not comfortable with Java OO development.This (fully Java based API on top of POSIX kenel) is the future.
This is where Linux desktop should be.
The reason for the sad state of the Linux desktop is that C API make it too difficult to create applications more complex trivial.
At this point the choice is between .NET and Java.
Of course Google choose Java.I have been looking at the API and the architecture of Android and I am very impressed.
It looks very UNIX'ish in many areas.
Just consider how they deal with "process groups".
It's like POSIX process groups taken to GUI applications level.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738590</id>
	<title>Re:dumb article/crappy developer</title>
	<author>Unoti</author>
	<datestamp>1263317340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You're not missing something, you're right on.  His point 5, tyranny of the commons, is generally not a problem.  With the exception of services, apps don't keep on running.  With regard to memory, each app is limited to 16M.  That's generally a small enough value that in the minimum configuration for Android-- 64 megs-- the app can run.  When the user switches applications, it is up to the OS to decide how long and whether to leave that memory allocated to your app.</p><p>If anything, the opposite of the tyranny of the commons is a problem: you can't really use all the resources available in the device in the app (for memory at least), potentially leaving the device underutilized.</p></htmltext>
<tokenext>You 're not missing something , you 're right on .
His point 5 , tyranny of the commons , is generally not a problem .
With the exception of services , apps do n't keep on running .
With regard to memory , each app is limited to 16M .
That 's generally a small enough value that in the minimum configuration for Android-- 64 megs-- the app can run .
When the user switches applications , it is up to the OS to decide how long and whether to leave that memory allocated to your app.If anything , the opposite of the tyranny of the commons is a problem : you ca n't really use all the resources available in the device in the app ( for memory at least ) , potentially leaving the device underutilized .</tokentext>
<sentencetext>You're not missing something, you're right on.
His point 5, tyranny of the commons, is generally not a problem.
With the exception of services, apps don't keep on running.
With regard to memory, each app is limited to 16M.
That's generally a small enough value that in the minimum configuration for Android-- 64 megs-- the app can run.
When the user switches applications, it is up to the OS to decide how long and whether to leave that memory allocated to your app.If anything, the opposite of the tyranny of the commons is a problem: you can't really use all the resources available in the device in the app (for memory at least), potentially leaving the device underutilized.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736446</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30745878</id>
	<title>Re:What?</title>
	<author>Eil</author>
	<datestamp>1263307140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Android makes it way to easy to build simple apps but makes t more difficult to produce top notch professional apps than the iPhone does.</p></div></blockquote><p>You must point me to these top-notch professional apps on the iPhone/iPod, because I haven't seen any yet.</p><p>I bought an iPod Touch three weeks ago and so far have found that its primary redeeming quality is the excellent web browser. Not much else has really lived up to all of the hype I've been hearing over the past couple years. Even though it carries the iPod name, the UI for navigating and playing audio and video really sucks. Podcast management (the main reason I bought the device) is particularly dismal and there are no downloadable alternatives since Apple forbids it. I've generally found that most applications in the App Store fall into these four categories:</p><p>1. Apps which make trivial use of the iPod/iPhone hardware (flashlights, compasses, voice recorders, etc)<br>2. Content delivery for existing publications, stores and websites (CNN, New York Times, Facebook, etc)<br>3. Casual games (Tetris, Bejewelled, etc)<br>4. Personal computation/information software (Tip calculators, notepads, budget apps, currency converters, etc)</p><p>I haven't seen a single app yet that I would consider paying actual money for. Maybe it's just because I'm a geek and am therefore difficult to "wow" when it comes to technology, but the point remains. I jailbroke my iPod, but all that really opens up is an adware-supported application installer and shell access to the device. Even many of the jailbreak-only apps seem to be driven by the same "must monetize everything" iPhone development mentality.</p><p>The second someone comes out with an iPod Touch equivalent running a full version of Android, I'll be all over it. I'd love to give the N900 a whirl but it costs twice as much as I'd ever pay and the N800 put me off as far as Maemo is concerned.</p></div>
	</htmltext>
<tokenext>Android makes it way to easy to build simple apps but makes t more difficult to produce top notch professional apps than the iPhone does.You must point me to these top-notch professional apps on the iPhone/iPod , because I have n't seen any yet.I bought an iPod Touch three weeks ago and so far have found that its primary redeeming quality is the excellent web browser .
Not much else has really lived up to all of the hype I 've been hearing over the past couple years .
Even though it carries the iPod name , the UI for navigating and playing audio and video really sucks .
Podcast management ( the main reason I bought the device ) is particularly dismal and there are no downloadable alternatives since Apple forbids it .
I 've generally found that most applications in the App Store fall into these four categories : 1 .
Apps which make trivial use of the iPod/iPhone hardware ( flashlights , compasses , voice recorders , etc ) 2 .
Content delivery for existing publications , stores and websites ( CNN , New York Times , Facebook , etc ) 3 .
Casual games ( Tetris , Bejewelled , etc ) 4 .
Personal computation/information software ( Tip calculators , notepads , budget apps , currency converters , etc ) I have n't seen a single app yet that I would consider paying actual money for .
Maybe it 's just because I 'm a geek and am therefore difficult to " wow " when it comes to technology , but the point remains .
I jailbroke my iPod , but all that really opens up is an adware-supported application installer and shell access to the device .
Even many of the jailbreak-only apps seem to be driven by the same " must monetize everything " iPhone development mentality.The second someone comes out with an iPod Touch equivalent running a full version of Android , I 'll be all over it .
I 'd love to give the N900 a whirl but it costs twice as much as I 'd ever pay and the N800 put me off as far as Maemo is concerned .</tokentext>
<sentencetext>Android makes it way to easy to build simple apps but makes t more difficult to produce top notch professional apps than the iPhone does.You must point me to these top-notch professional apps on the iPhone/iPod, because I haven't seen any yet.I bought an iPod Touch three weeks ago and so far have found that its primary redeeming quality is the excellent web browser.
Not much else has really lived up to all of the hype I've been hearing over the past couple years.
Even though it carries the iPod name, the UI for navigating and playing audio and video really sucks.
Podcast management (the main reason I bought the device) is particularly dismal and there are no downloadable alternatives since Apple forbids it.
I've generally found that most applications in the App Store fall into these four categories:1.
Apps which make trivial use of the iPod/iPhone hardware (flashlights, compasses, voice recorders, etc)2.
Content delivery for existing publications, stores and websites (CNN, New York Times, Facebook, etc)3.
Casual games (Tetris, Bejewelled, etc)4.
Personal computation/information software (Tip calculators, notepads, budget apps, currency converters, etc)I haven't seen a single app yet that I would consider paying actual money for.
Maybe it's just because I'm a geek and am therefore difficult to "wow" when it comes to technology, but the point remains.
I jailbroke my iPod, but all that really opens up is an adware-supported application installer and shell access to the device.
Even many of the jailbreak-only apps seem to be driven by the same "must monetize everything" iPhone development mentality.The second someone comes out with an iPod Touch equivalent running a full version of Android, I'll be all over it.
I'd love to give the N900 a whirl but it costs twice as much as I'd ever pay and the N800 put me off as far as Maemo is concerned.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737098</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737158</id>
	<title>Re:dumb article/crappy developer</title>
	<author>MikeBabcock</author>
	<datestamp>1263311940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The OS already closes those apps for you.  The system never actually runs out of memory, does it?  I wish it were slightly more aggressive sometimes (and some of the task managers simply lower the high water mark to achieve this), but for the most part it works.</p><p>I can run my weather software, then check my mail, click a link in my mail to Dolphin (the browser), and subscribe to the feed in Google Reader without much of a hiccup in between -- on an old HTC Dream phone.  Granted, its even faster since moving up to 1.6 via Cyanogen.</p></htmltext>
<tokenext>The OS already closes those apps for you .
The system never actually runs out of memory , does it ?
I wish it were slightly more aggressive sometimes ( and some of the task managers simply lower the high water mark to achieve this ) , but for the most part it works.I can run my weather software , then check my mail , click a link in my mail to Dolphin ( the browser ) , and subscribe to the feed in Google Reader without much of a hiccup in between -- on an old HTC Dream phone .
Granted , its even faster since moving up to 1.6 via Cyanogen .</tokentext>
<sentencetext>The OS already closes those apps for you.
The system never actually runs out of memory, does it?
I wish it were slightly more aggressive sometimes (and some of the task managers simply lower the high water mark to achieve this), but for the most part it works.I can run my weather software, then check my mail, click a link in my mail to Dolphin (the browser), and subscribe to the feed in Google Reader without much of a hiccup in between -- on an old HTC Dream phone.
Granted, its even faster since moving up to 1.6 via Cyanogen.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739592</id>
	<title>He's right and he's wrong</title>
	<author>amoeba1911</author>
	<datestamp>1263320760000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>
This guys is right in some places, wrong in some others. Changing screen orientation restarts the Activity, but you can tell it in your manifest that you don't want it to automatically restart the Activity on orientation change, giving you the control to do whatever you want.
</p><p>
Android forces you to make the application centered around the Activities, but it's not so bad when you get used to it. It's not necessarily bad, just a bit different.
</p><p>
The debugging? He's definitely being an idiot about this. How is easy debugging a gripe? He's griping that it makes it easier to debug? No, that's just idiotic. Debugging on the Android is very easy and that's a good thing, not bad.
</p><p>
Applications never, ever quit? No, that's not true. I made my app quit save and quit when it goes to background. Other people's apps don't quit. You want your app to quit, you can make it so it quits. Also, if app doesn't quit and goes to background, android will automatically close the background app if it needs the resources to run foreground apps. So they do quit, you can program the app to quit, so he's just plain wrong.
</p><p>
He mentions Java... yes, Java sucks for this. The phone is not very fast to begin with, and running a slow bloated language like Java isn't necessarily the best thing. Java is good for people who don't know how to work with pointers and de-allocate memory, Java is good for people who don't understand programming who want to program things and Java pays for it in performance. Java is like a tricycle compared to low level languages. But the good thing is: it's harder to fall off a tricycle and hurt yourself. With a real programming language you might run into huge problems, late night debugging sessions trying to find where your mistake is. With Java you're playing it safe. Thankfully they provided a NDK, but that's a real pain in the ass, has the speed you want, then has the drawbacks too. <br>
You can get around Java's slowness by following their program optimization guidelines, things like: don't use too many classes, cache calculation results instead of recalculating things, use native java functions ie use indexOf instead of looping through a string. It makes Java bearable.
</p><p>
He mentions platform fragmentation. The main difference between Android devices is their different sized screens. Honestly, that shouldn't be an issue, using XML interface it should all look pretty much the same. If you're doing fancy graphics, you have to be smart and use percentages instead of hard coded sizes for things. Coming from a PC background where users might be running 640x480 or 1600x1200, I think we're all familiar with different screen sizes and how to handle them. Going from 320x480 to 240x320 shouldn't be much trouble for a competent programmer. If you can't handle it, stick to XML interface.
</p><p>
So: Android developing might have it's shortcomings, but they're not as bad as this guy makes it sound. Easy debugging is definitely NOT a shortfall. Also, you can download the android SDK + emulator for free, it runs on Mac, Linux, Windows. Compare that to iPhone, you need to pay $100/year to get the SDK, and even after you get it, you can't run it unless you have a Mac.
</p></htmltext>
<tokenext>This guys is right in some places , wrong in some others .
Changing screen orientation restarts the Activity , but you can tell it in your manifest that you do n't want it to automatically restart the Activity on orientation change , giving you the control to do whatever you want .
Android forces you to make the application centered around the Activities , but it 's not so bad when you get used to it .
It 's not necessarily bad , just a bit different .
The debugging ?
He 's definitely being an idiot about this .
How is easy debugging a gripe ?
He 's griping that it makes it easier to debug ?
No , that 's just idiotic .
Debugging on the Android is very easy and that 's a good thing , not bad .
Applications never , ever quit ?
No , that 's not true .
I made my app quit save and quit when it goes to background .
Other people 's apps do n't quit .
You want your app to quit , you can make it so it quits .
Also , if app does n't quit and goes to background , android will automatically close the background app if it needs the resources to run foreground apps .
So they do quit , you can program the app to quit , so he 's just plain wrong .
He mentions Java... yes , Java sucks for this .
The phone is not very fast to begin with , and running a slow bloated language like Java is n't necessarily the best thing .
Java is good for people who do n't know how to work with pointers and de-allocate memory , Java is good for people who do n't understand programming who want to program things and Java pays for it in performance .
Java is like a tricycle compared to low level languages .
But the good thing is : it 's harder to fall off a tricycle and hurt yourself .
With a real programming language you might run into huge problems , late night debugging sessions trying to find where your mistake is .
With Java you 're playing it safe .
Thankfully they provided a NDK , but that 's a real pain in the ass , has the speed you want , then has the drawbacks too .
You can get around Java 's slowness by following their program optimization guidelines , things like : do n't use too many classes , cache calculation results instead of recalculating things , use native java functions ie use indexOf instead of looping through a string .
It makes Java bearable .
He mentions platform fragmentation .
The main difference between Android devices is their different sized screens .
Honestly , that should n't be an issue , using XML interface it should all look pretty much the same .
If you 're doing fancy graphics , you have to be smart and use percentages instead of hard coded sizes for things .
Coming from a PC background where users might be running 640x480 or 1600x1200 , I think we 're all familiar with different screen sizes and how to handle them .
Going from 320x480 to 240x320 should n't be much trouble for a competent programmer .
If you ca n't handle it , stick to XML interface .
So : Android developing might have it 's shortcomings , but they 're not as bad as this guy makes it sound .
Easy debugging is definitely NOT a shortfall .
Also , you can download the android SDK + emulator for free , it runs on Mac , Linux , Windows .
Compare that to iPhone , you need to pay $ 100/year to get the SDK , and even after you get it , you ca n't run it unless you have a Mac .</tokentext>
<sentencetext>
This guys is right in some places, wrong in some others.
Changing screen orientation restarts the Activity, but you can tell it in your manifest that you don't want it to automatically restart the Activity on orientation change, giving you the control to do whatever you want.
Android forces you to make the application centered around the Activities, but it's not so bad when you get used to it.
It's not necessarily bad, just a bit different.
The debugging?
He's definitely being an idiot about this.
How is easy debugging a gripe?
He's griping that it makes it easier to debug?
No, that's just idiotic.
Debugging on the Android is very easy and that's a good thing, not bad.
Applications never, ever quit?
No, that's not true.
I made my app quit save and quit when it goes to background.
Other people's apps don't quit.
You want your app to quit, you can make it so it quits.
Also, if app doesn't quit and goes to background, android will automatically close the background app if it needs the resources to run foreground apps.
So they do quit, you can program the app to quit, so he's just plain wrong.
He mentions Java... yes, Java sucks for this.
The phone is not very fast to begin with, and running a slow bloated language like Java isn't necessarily the best thing.
Java is good for people who don't know how to work with pointers and de-allocate memory, Java is good for people who don't understand programming who want to program things and Java pays for it in performance.
Java is like a tricycle compared to low level languages.
But the good thing is: it's harder to fall off a tricycle and hurt yourself.
With a real programming language you might run into huge problems, late night debugging sessions trying to find where your mistake is.
With Java you're playing it safe.
Thankfully they provided a NDK, but that's a real pain in the ass, has the speed you want, then has the drawbacks too.
You can get around Java's slowness by following their program optimization guidelines, things like: don't use too many classes, cache calculation results instead of recalculating things, use native java functions ie use indexOf instead of looping through a string.
It makes Java bearable.
He mentions platform fragmentation.
The main difference between Android devices is their different sized screens.
Honestly, that shouldn't be an issue, using XML interface it should all look pretty much the same.
If you're doing fancy graphics, you have to be smart and use percentages instead of hard coded sizes for things.
Coming from a PC background where users might be running 640x480 or 1600x1200, I think we're all familiar with different screen sizes and how to handle them.
Going from 320x480 to 240x320 shouldn't be much trouble for a competent programmer.
If you can't handle it, stick to XML interface.
So: Android developing might have it's shortcomings, but they're not as bad as this guy makes it sound.
Easy debugging is definitely NOT a shortfall.
Also, you can download the android SDK + emulator for free, it runs on Mac, Linux, Windows.
Compare that to iPhone, you need to pay $100/year to get the SDK, and even after you get it, you can't run it unless you have a Mac.
</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737134</id>
	<title>Re:why Java?</title>
	<author>Josh04</author>
	<datestamp>1263311820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Neither 1 nor 2 is an argument for not using java, and 3 isn't really applicable as not only is it optimised for it's own version of java, but you have the option of writing C anyway.</htmltext>
<tokenext>Neither 1 nor 2 is an argument for not using java , and 3 is n't really applicable as not only is it optimised for it 's own version of java , but you have the option of writing C anyway .</tokentext>
<sentencetext>Neither 1 nor 2 is an argument for not using java, and 3 isn't really applicable as not only is it optimised for it's own version of java, but you have the option of writing C anyway.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288</id>
	<title>5. Developer Cooperative</title>
	<author>Unoti</author>
	<datestamp>1263312480000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p> tragedy of the commons: the misuse and overuse of a collectively owned resource. In the case of Android, that common resource is the memory, processor, and battery life of the handset. The tragedy is that any application, while in the background, can use any amount of resources.</p></div></blockquote><p>
This isn't exactly true.  Apps only get to use 16 megs of memory on Android.  Sounds like a lot, but it's not, especially if you're working with 2d graphics. That's actually something that's causing a lot of difficulty for me in game development on Android.  A 1000x800 image is 3.2 megs by itself (1000 x 800 x 4 bytes per pixel). Put a couple of sprite sheets into memory for animation and you're rubbing elbows with the limits.</p><p>The point from the article about apps being unconstrained and able to ruin each other isn't really true, at least not for memory.  Perhaps the problem the author cites is more of a problem on Android platforms with only 64megs of memory to work with in total.  On my Droid, I am saddened by the opposite problem: only being able to use a small portion of my device's memory.</p></div>
	</htmltext>
<tokenext>tragedy of the commons : the misuse and overuse of a collectively owned resource .
In the case of Android , that common resource is the memory , processor , and battery life of the handset .
The tragedy is that any application , while in the background , can use any amount of resources .
This is n't exactly true .
Apps only get to use 16 megs of memory on Android .
Sounds like a lot , but it 's not , especially if you 're working with 2d graphics .
That 's actually something that 's causing a lot of difficulty for me in game development on Android .
A 1000x800 image is 3.2 megs by itself ( 1000 x 800 x 4 bytes per pixel ) .
Put a couple of sprite sheets into memory for animation and you 're rubbing elbows with the limits.The point from the article about apps being unconstrained and able to ruin each other is n't really true , at least not for memory .
Perhaps the problem the author cites is more of a problem on Android platforms with only 64megs of memory to work with in total .
On my Droid , I am saddened by the opposite problem : only being able to use a small portion of my device 's memory .</tokentext>
<sentencetext> tragedy of the commons: the misuse and overuse of a collectively owned resource.
In the case of Android, that common resource is the memory, processor, and battery life of the handset.
The tragedy is that any application, while in the background, can use any amount of resources.
This isn't exactly true.
Apps only get to use 16 megs of memory on Android.
Sounds like a lot, but it's not, especially if you're working with 2d graphics.
That's actually something that's causing a lot of difficulty for me in game development on Android.
A 1000x800 image is 3.2 megs by itself (1000 x 800 x 4 bytes per pixel).
Put a couple of sprite sheets into memory for animation and you're rubbing elbows with the limits.The point from the article about apps being unconstrained and able to ruin each other isn't really true, at least not for memory.
Perhaps the problem the author cites is more of a problem on Android platforms with only 64megs of memory to work with in total.
On my Droid, I am saddened by the opposite problem: only being able to use a small portion of my device's memory.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366</id>
	<title>Re:Unix way</title>
	<author>numbski</author>
	<datestamp>1263308280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I know there's at least one open source project that does what OSX does with it's<nobr> <wbr></nobr>.app bundles, but I'm really surprised that the<nobr> <wbr></nobr>.app way of packaging applications for drag-and-drop use hasn't caught on with the rest of the Unix-like OS community.  The only reason I can think of off-hand is the architecture concerns - x86 vs x86-64 vs ppc vs arm, etc, but we already live with this today using things like apt and yum.  Disk space is cheap, and largely, so is bandwidth.  I really don't mind having 10 copies of a library so long as they're known to work with whatever version of application x I have, but not screw with application y.  For userland applications, it would completely obliterate the concern for dependencies.  The downside of course is that instead of `aptitude update &amp;&amp; aptitude upgrade` going through and updating *everything* for you, you now have to either have your applications phoning home to check for new versions or the user has to keep up with the latest version themselves (a la VersionTracker for OSX).</p><p>I prefer unix personally, and all of my machines are some flavor of it - but man it would push adoption if applications where able to be installed by simply downloading, drag-and-drop.  Either that or have it possible via a link to launch Synaptic and start the installation from the program's website.  For the user's part, you've now actually made installation *easier* than Windows but the steps involved are similar.</p><p>Actually - that latter idea, has it already been implemented?  If not, I need to go submit some enhancement requests.<nobr> <wbr></nobr>:P</p></htmltext>
<tokenext>I know there 's at least one open source project that does what OSX does with it 's .app bundles , but I 'm really surprised that the .app way of packaging applications for drag-and-drop use has n't caught on with the rest of the Unix-like OS community .
The only reason I can think of off-hand is the architecture concerns - x86 vs x86-64 vs ppc vs arm , etc , but we already live with this today using things like apt and yum .
Disk space is cheap , and largely , so is bandwidth .
I really do n't mind having 10 copies of a library so long as they 're known to work with whatever version of application x I have , but not screw with application y. For userland applications , it would completely obliterate the concern for dependencies .
The downside of course is that instead of ` aptitude update &amp;&amp; aptitude upgrade ` going through and updating * everything * for you , you now have to either have your applications phoning home to check for new versions or the user has to keep up with the latest version themselves ( a la VersionTracker for OSX ) .I prefer unix personally , and all of my machines are some flavor of it - but man it would push adoption if applications where able to be installed by simply downloading , drag-and-drop .
Either that or have it possible via a link to launch Synaptic and start the installation from the program 's website .
For the user 's part , you 've now actually made installation * easier * than Windows but the steps involved are similar.Actually - that latter idea , has it already been implemented ?
If not , I need to go submit some enhancement requests .
: P</tokentext>
<sentencetext>I know there's at least one open source project that does what OSX does with it's .app bundles, but I'm really surprised that the .app way of packaging applications for drag-and-drop use hasn't caught on with the rest of the Unix-like OS community.
The only reason I can think of off-hand is the architecture concerns - x86 vs x86-64 vs ppc vs arm, etc, but we already live with this today using things like apt and yum.
Disk space is cheap, and largely, so is bandwidth.
I really don't mind having 10 copies of a library so long as they're known to work with whatever version of application x I have, but not screw with application y.  For userland applications, it would completely obliterate the concern for dependencies.
The downside of course is that instead of `aptitude update &amp;&amp; aptitude upgrade` going through and updating *everything* for you, you now have to either have your applications phoning home to check for new versions or the user has to keep up with the latest version themselves (a la VersionTracker for OSX).I prefer unix personally, and all of my machines are some flavor of it - but man it would push adoption if applications where able to be installed by simply downloading, drag-and-drop.
Either that or have it possible via a link to launch Synaptic and start the installation from the program's website.
For the user's part, you've now actually made installation *easier* than Windows but the steps involved are similar.Actually - that latter idea, has it already been implemented?
If not, I need to go submit some enhancement requests.
:P</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736056</id>
	<title>Re:What?</title>
	<author>Anonymous</author>
	<datestamp>1263306360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you're focusing on his one lanky point, then you're missing the point of the article: which is that a LOT of things are messed up on android.</p><p>In reality he is concerned about google's lack of actual open source - since apache is like BSD license, guess what happens? The important pieces are kept proprietary in the code, and that creates problems.</p><p>the other programming issues and google quirks were equally very accurate. Fragmentation and having piss poor hardware except for a couple phones is also an issue.</p><p>From the G1 in comparison to every android phone since and the nexus one of now, every phone has been basically creeping closer to iphone performance...now they finally have better hardware, but on a shitty touchscreen.</p><p>Google has a lot to fix, and I don't know the answers. Open sourcing their maps and other currently locked down apps would be a good start.</p></htmltext>
<tokenext>If you 're focusing on his one lanky point , then you 're missing the point of the article : which is that a LOT of things are messed up on android.In reality he is concerned about google 's lack of actual open source - since apache is like BSD license , guess what happens ?
The important pieces are kept proprietary in the code , and that creates problems.the other programming issues and google quirks were equally very accurate .
Fragmentation and having piss poor hardware except for a couple phones is also an issue.From the G1 in comparison to every android phone since and the nexus one of now , every phone has been basically creeping closer to iphone performance...now they finally have better hardware , but on a shitty touchscreen.Google has a lot to fix , and I do n't know the answers .
Open sourcing their maps and other currently locked down apps would be a good start .</tokentext>
<sentencetext>If you're focusing on his one lanky point, then you're missing the point of the article: which is that a LOT of things are messed up on android.In reality he is concerned about google's lack of actual open source - since apache is like BSD license, guess what happens?
The important pieces are kept proprietary in the code, and that creates problems.the other programming issues and google quirks were equally very accurate.
Fragmentation and having piss poor hardware except for a couple phones is also an issue.From the G1 in comparison to every android phone since and the nexus one of now, every phone has been basically creeping closer to iphone performance...now they finally have better hardware, but on a shitty touchscreen.Google has a lot to fix, and I don't know the answers.
Open sourcing their maps and other currently locked down apps would be a good start.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736992</id>
	<title>Re:dumb article/crappy developer</title>
	<author>GooberToo</author>
	<datestamp>1263311400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The biggest reason he gives while this is bad is because it destroys then recreates an activity upon rotating the screen</p></div><p>That's the default. The behavior can be overridden such that the activity is not destroyed and recreated.</p></div>
	</htmltext>
<tokenext>The biggest reason he gives while this is bad is because it destroys then recreates an activity upon rotating the screenThat 's the default .
The behavior can be overridden such that the activity is not destroyed and recreated .</tokentext>
<sentencetext>The biggest reason he gives while this is bad is because it destroys then recreates an activity upon rotating the screenThat's the default.
The behavior can be overridden such that the activity is not destroyed and recreated.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736270</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737098</id>
	<title>Re:What?</title>
	<author>LWATCDR</author>
	<datestamp>1263311700000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Not really.<br>He hates Java. A lot of people seem to feel that way. I actually like Java more than say c++ because I find the Java object model has a less of a tacked on feel.<br>The big problem is that he doesn't like the "fragmentation" which is a valid concern for a developer. You have a number of different screen sizes to deal with, you have a number of different cpus that run at differn't speed to deal with you way to many different versions to deal with, and you have what ever custom sillyness that the vendors may put in to deal with.<br>On thing that is very nice for developers about the iPhone is that it is a very consistant controlled enviroment. It is much more like developing for say a game console than for a PC. That makes hidden gotchas less of an issue.<br>Android is a lot more like a PC.<br>So you are half right.<br>Android makes it way to easy to build simple apps but makes t more difficult to produce top notch professional apps than the iPhone does.<br>How true that is I don't know since I have yet to dive into the Android SDK but even now I wonder which SDK do I write too? 1.5 which seems to be the most common. 1.6, 2.0, or do I leap to 2.1 and hope everybody updates by the time my app is done?<br>It is EXTREMELY annoying that there are so many different versions of an OS all of which are shipping on phones right this second!</p></htmltext>
<tokenext>Not really.He hates Java .
A lot of people seem to feel that way .
I actually like Java more than say c + + because I find the Java object model has a less of a tacked on feel.The big problem is that he does n't like the " fragmentation " which is a valid concern for a developer .
You have a number of different screen sizes to deal with , you have a number of different cpus that run at differ n't speed to deal with you way to many different versions to deal with , and you have what ever custom sillyness that the vendors may put in to deal with.On thing that is very nice for developers about the iPhone is that it is a very consistant controlled enviroment .
It is much more like developing for say a game console than for a PC .
That makes hidden gotchas less of an issue.Android is a lot more like a PC.So you are half right.Android makes it way to easy to build simple apps but makes t more difficult to produce top notch professional apps than the iPhone does.How true that is I do n't know since I have yet to dive into the Android SDK but even now I wonder which SDK do I write too ?
1.5 which seems to be the most common .
1.6 , 2.0 , or do I leap to 2.1 and hope everybody updates by the time my app is done ? It is EXTREMELY annoying that there are so many different versions of an OS all of which are shipping on phones right this second !</tokentext>
<sentencetext>Not really.He hates Java.
A lot of people seem to feel that way.
I actually like Java more than say c++ because I find the Java object model has a less of a tacked on feel.The big problem is that he doesn't like the "fragmentation" which is a valid concern for a developer.
You have a number of different screen sizes to deal with, you have a number of different cpus that run at differn't speed to deal with you way to many different versions to deal with, and you have what ever custom sillyness that the vendors may put in to deal with.On thing that is very nice for developers about the iPhone is that it is a very consistant controlled enviroment.
It is much more like developing for say a game console than for a PC.
That makes hidden gotchas less of an issue.Android is a lot more like a PC.So you are half right.Android makes it way to easy to build simple apps but makes t more difficult to produce top notch professional apps than the iPhone does.How true that is I don't know since I have yet to dive into the Android SDK but even now I wonder which SDK do I write too?
1.5 which seems to be the most common.
1.6, 2.0, or do I leap to 2.1 and hope everybody updates by the time my app is done?It is EXTREMELY annoying that there are so many different versions of an OS all of which are shipping on phones right this second!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743676</id>
	<title>Re:5. Developer Cooperative</title>
	<author>pjt33</author>
	<datestamp>1263295320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No support for palettes? Or do you really need 32-bit colour?</p></htmltext>
<tokenext>No support for palettes ?
Or do you really need 32-bit colour ?</tokentext>
<sentencetext>No support for palettes?
Or do you really need 32-bit colour?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737418</id>
	<title>Re:What?</title>
	<author>StripedCow</author>
	<datestamp>1263312960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Perhaps his real problem is that google is commoditizing the software industry.</p><p>I'd say better get used to it, and start making real applications that serve a certain niche, instead of the mainstream applications that everybody uses.</p></htmltext>
<tokenext>Perhaps his real problem is that google is commoditizing the software industry.I 'd say better get used to it , and start making real applications that serve a certain niche , instead of the mainstream applications that everybody uses .</tokentext>
<sentencetext>Perhaps his real problem is that google is commoditizing the software industry.I'd say better get used to it, and start making real applications that serve a certain niche, instead of the mainstream applications that everybody uses.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737218</id>
	<title>Re:Unix way</title>
	<author>Aqualung812</author>
	<datestamp>1263312120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>My app, for example, can for example make use of Google's picture browsing or the google map activity , no need to write one myself.</p></div></blockquote><p>
Interesting.  How does Android protect against a rouge app stealing my Google contacts and mass-mailing out Google mail?</p></div>
	</htmltext>
<tokenext>My app , for example , can for example make use of Google 's picture browsing or the google map activity , no need to write one myself .
Interesting. How does Android protect against a rouge app stealing my Google contacts and mass-mailing out Google mail ?</tokentext>
<sentencetext>My app, for example, can for example make use of Google's picture browsing or the google map activity , no need to write one myself.
Interesting.  How does Android protect against a rouge app stealing my Google contacts and mass-mailing out Google mail?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736350</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736550</id>
	<title>Take if from an Android Dev</title>
	<author>derek5432</author>
	<datestamp>1263309480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This guy is a moron. Most of his "gripes" aren't even real gripes (e.g. the tools are too helpful!). The others aren't legitimate, except perhaps fragmentation, but that's inherent in the whole point of Android and the SDK has done a pretty good job so far of either letting you design for compatibility mode (in which Android tries to figure out the best way to render your UI) or design for 3 broad categories (basically small, medium, and large screens).

The guy really tips his hand when he talks about how Android hardware sucks. Check out this chart:

<a href="http://mashable.com/2010/01/05/nexus-one-vs-droid-vs-iphone/" title="mashable.com" rel="nofollow">http://mashable.com/2010/01/05/nexus-one-vs-droid-vs-iphone/</a> [mashable.com]

In terms of specs like screen and camera resolution, battery life, chipset, etc., the newest generation of Android devices are either comparable or surpass the iPhone.

The really stupid aspect of this article is that there are legitimate gripes about the platform that the author completely ignores. Huge on the list should be the inability of Android to run apps from the SD card, and thus the constraints on available space for apps on a device. The market still has all kinds of problems, the most dire a need for a decent desktop portal, something somewhere near comparable to iTunes. As far as the actual SDK, particular APIs are a chore to use (Google Maps, for example), and though Google rolls out new features with every SDK, they are often poorly documented (e.g., the new Account Manager API).

All in all, Android is great to develop for. But like every platform it's got its problems, and if you're going to gripe about it, do it right.</htmltext>
<tokenext>This guy is a moron .
Most of his " gripes " are n't even real gripes ( e.g .
the tools are too helpful ! ) .
The others are n't legitimate , except perhaps fragmentation , but that 's inherent in the whole point of Android and the SDK has done a pretty good job so far of either letting you design for compatibility mode ( in which Android tries to figure out the best way to render your UI ) or design for 3 broad categories ( basically small , medium , and large screens ) .
The guy really tips his hand when he talks about how Android hardware sucks .
Check out this chart : http : //mashable.com/2010/01/05/nexus-one-vs-droid-vs-iphone/ [ mashable.com ] In terms of specs like screen and camera resolution , battery life , chipset , etc. , the newest generation of Android devices are either comparable or surpass the iPhone .
The really stupid aspect of this article is that there are legitimate gripes about the platform that the author completely ignores .
Huge on the list should be the inability of Android to run apps from the SD card , and thus the constraints on available space for apps on a device .
The market still has all kinds of problems , the most dire a need for a decent desktop portal , something somewhere near comparable to iTunes .
As far as the actual SDK , particular APIs are a chore to use ( Google Maps , for example ) , and though Google rolls out new features with every SDK , they are often poorly documented ( e.g. , the new Account Manager API ) .
All in all , Android is great to develop for .
But like every platform it 's got its problems , and if you 're going to gripe about it , do it right .</tokentext>
<sentencetext>This guy is a moron.
Most of his "gripes" aren't even real gripes (e.g.
the tools are too helpful!).
The others aren't legitimate, except perhaps fragmentation, but that's inherent in the whole point of Android and the SDK has done a pretty good job so far of either letting you design for compatibility mode (in which Android tries to figure out the best way to render your UI) or design for 3 broad categories (basically small, medium, and large screens).
The guy really tips his hand when he talks about how Android hardware sucks.
Check out this chart:

http://mashable.com/2010/01/05/nexus-one-vs-droid-vs-iphone/ [mashable.com]

In terms of specs like screen and camera resolution, battery life, chipset, etc., the newest generation of Android devices are either comparable or surpass the iPhone.
The really stupid aspect of this article is that there are legitimate gripes about the platform that the author completely ignores.
Huge on the list should be the inability of Android to run apps from the SD card, and thus the constraints on available space for apps on a device.
The market still has all kinds of problems, the most dire a need for a decent desktop portal, something somewhere near comparable to iTunes.
As far as the actual SDK, particular APIs are a chore to use (Google Maps, for example), and though Google rolls out new features with every SDK, they are often poorly documented (e.g., the new Account Manager API).
All in all, Android is great to develop for.
But like every platform it's got its problems, and if you're going to gripe about it, do it right.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736496</id>
	<title>Obviously an inexperienced Android developer</title>
	<author>Maxmin</author>
	<datestamp>1263309180000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>1. What are you complaining about?  Of course it's a legal grey area, those are some of Google's primary products - why would they make it easy for you to slap Google Maps into a thin wrapper, insert adverts, and call it "Chris's Maps"?  Go write your own, silly boy.</p><p>2. You are required to declare *exactly one* activity and intent.  After that, it's up to you how you stitch together your app's UI elements.  The point of multiple Activitys is that they're a) modular, b) stackable, c) can be swapped during low memory events, and d) can have their state preserved by the platform upon exit.  Personally, I prefer a low number of activities, then use other UI elements to add navigational depth.</p><p>3. New to software development, eh?  Over the next 5-10 years, be prepared to learn new and discard old, that's the profession you've entered (recently, it seems.)</p><p>4. "Never quitting" is merely the default.  It's up to you to detect navigational or logical termination of your app, and invoke the necessary methods to bring it to an end.  The reason for this is that, hey! it's a phone, call might come in!  and it's a multitasking O/S!  Another app's Activity may suddenly be running on top of yours, and you may not want to exit just yet, hmm?</p><p>5. Finally, a real problem.  Yes, there are apps that leave background processes running continuosly, disregarding the device's sleep state.  These are from bad developers -- learn well from their mistakes.  Also, you don't have to use those apps, just uninstall them, and also install Power Manager which will extend your battery life.</p><p>6. Watch the video "<a href="http://code.google.com/events/io/2009/sessions/WritingRealTimeGamesAndroid.html" title="google.com">Writing Real-time Games for Android</a> [google.com]," wherein you will be introduced to some key concepts around embedded and real-time software development.  First and foremost, STOP DOING THINGS THAT INVOKE THE GC!  Cool it with excessive + string + concatenation and start using StringBuffer.  And preallocate objects to that end as well.  Et cetera.</p><p>7. Intense, dude.  Having developed for Blackberry, all I can do is throw my head back and laugh, laugh hard.  Android is a V12 Ferrari next to Blackberry's three-cylindar commuter tin can.</p><p>8. If you'd read Google's Android documentation, you'd realize this point was moot, thanks to the carefully spelled-out guidelines that will keep your app looking and behaving the same across various screen sizes.  True that you'll have to *think* about how to handle an 8x10 format screen in your app, but that's no different than any windowed platform.</p><p>9. You start out whining about "platform fragmentation," then return to your point #1.  Whatever.  Platform fragmentation may, indeed, become a problem one day, but you haven't defined how that will happen, in your point.</p><p>10. If I'm not mistaken, Nexus One equals (or eclipses) the iPhone's raw computing power.  1 GHz, GPU, though low on RAM and flash comparatively.  I'd rather have a platform with greater RAM, but the architecture of Android is such that it is *meant* to run on low-capability devices.</p><p>Apart from the author being a newbie, did we all misread it as not being a spoof??</p></htmltext>
<tokenext>1 .
What are you complaining about ?
Of course it 's a legal grey area , those are some of Google 's primary products - why would they make it easy for you to slap Google Maps into a thin wrapper , insert adverts , and call it " Chris 's Maps " ?
Go write your own , silly boy.2 .
You are required to declare * exactly one * activity and intent .
After that , it 's up to you how you stitch together your app 's UI elements .
The point of multiple Activitys is that they 're a ) modular , b ) stackable , c ) can be swapped during low memory events , and d ) can have their state preserved by the platform upon exit .
Personally , I prefer a low number of activities , then use other UI elements to add navigational depth.3 .
New to software development , eh ?
Over the next 5-10 years , be prepared to learn new and discard old , that 's the profession you 've entered ( recently , it seems. ) 4 .
" Never quitting " is merely the default .
It 's up to you to detect navigational or logical termination of your app , and invoke the necessary methods to bring it to an end .
The reason for this is that , hey !
it 's a phone , call might come in !
and it 's a multitasking O/S !
Another app 's Activity may suddenly be running on top of yours , and you may not want to exit just yet , hmm ? 5 .
Finally , a real problem .
Yes , there are apps that leave background processes running continuosly , disregarding the device 's sleep state .
These are from bad developers -- learn well from their mistakes .
Also , you do n't have to use those apps , just uninstall them , and also install Power Manager which will extend your battery life.6 .
Watch the video " Writing Real-time Games for Android [ google.com ] , " wherein you will be introduced to some key concepts around embedded and real-time software development .
First and foremost , STOP DOING THINGS THAT INVOKE THE GC !
Cool it with excessive + string + concatenation and start using StringBuffer .
And preallocate objects to that end as well .
Et cetera.7 .
Intense , dude .
Having developed for Blackberry , all I can do is throw my head back and laugh , laugh hard .
Android is a V12 Ferrari next to Blackberry 's three-cylindar commuter tin can.8 .
If you 'd read Google 's Android documentation , you 'd realize this point was moot , thanks to the carefully spelled-out guidelines that will keep your app looking and behaving the same across various screen sizes .
True that you 'll have to * think * about how to handle an 8x10 format screen in your app , but that 's no different than any windowed platform.9 .
You start out whining about " platform fragmentation , " then return to your point # 1 .
Whatever. Platform fragmentation may , indeed , become a problem one day , but you have n't defined how that will happen , in your point.10 .
If I 'm not mistaken , Nexus One equals ( or eclipses ) the iPhone 's raw computing power .
1 GHz , GPU , though low on RAM and flash comparatively .
I 'd rather have a platform with greater RAM , but the architecture of Android is such that it is * meant * to run on low-capability devices.Apart from the author being a newbie , did we all misread it as not being a spoof ?
?</tokentext>
<sentencetext>1.
What are you complaining about?
Of course it's a legal grey area, those are some of Google's primary products - why would they make it easy for you to slap Google Maps into a thin wrapper, insert adverts, and call it "Chris's Maps"?
Go write your own, silly boy.2.
You are required to declare *exactly one* activity and intent.
After that, it's up to you how you stitch together your app's UI elements.
The point of multiple Activitys is that they're a) modular, b) stackable, c) can be swapped during low memory events, and d) can have their state preserved by the platform upon exit.
Personally, I prefer a low number of activities, then use other UI elements to add navigational depth.3.
New to software development, eh?
Over the next 5-10 years, be prepared to learn new and discard old, that's the profession you've entered (recently, it seems.)4.
"Never quitting" is merely the default.
It's up to you to detect navigational or logical termination of your app, and invoke the necessary methods to bring it to an end.
The reason for this is that, hey!
it's a phone, call might come in!
and it's a multitasking O/S!
Another app's Activity may suddenly be running on top of yours, and you may not want to exit just yet, hmm?5.
Finally, a real problem.
Yes, there are apps that leave background processes running continuosly, disregarding the device's sleep state.
These are from bad developers -- learn well from their mistakes.
Also, you don't have to use those apps, just uninstall them, and also install Power Manager which will extend your battery life.6.
Watch the video "Writing Real-time Games for Android [google.com]," wherein you will be introduced to some key concepts around embedded and real-time software development.
First and foremost, STOP DOING THINGS THAT INVOKE THE GC!
Cool it with excessive + string + concatenation and start using StringBuffer.
And preallocate objects to that end as well.
Et cetera.7.
Intense, dude.
Having developed for Blackberry, all I can do is throw my head back and laugh, laugh hard.
Android is a V12 Ferrari next to Blackberry's three-cylindar commuter tin can.8.
If you'd read Google's Android documentation, you'd realize this point was moot, thanks to the carefully spelled-out guidelines that will keep your app looking and behaving the same across various screen sizes.
True that you'll have to *think* about how to handle an 8x10 format screen in your app, but that's no different than any windowed platform.9.
You start out whining about "platform fragmentation," then return to your point #1.
Whatever.  Platform fragmentation may, indeed, become a problem one day, but you haven't defined how that will happen, in your point.10.
If I'm not mistaken, Nexus One equals (or eclipses) the iPhone's raw computing power.
1 GHz, GPU, though low on RAM and flash comparatively.
I'd rather have a platform with greater RAM, but the architecture of Android is such that it is *meant* to run on low-capability devices.Apart from the author being a newbie, did we all misread it as not being a spoof?
?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746358</id>
	<title>Platform Fragmentation</title>
	<author>foxylad</author>
	<datestamp>1263311100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If we cast our minds back twenty years, the same choice faced developers - did you make apps for the nice stable hardware-controlled Mac, or for the chaotic IBM PC compatible world?</p><p>Two points: first, it's an amazing reflection on Apple's success that they are a player in both of these choices.</p><p>Second, I think the relative success of iphone/android will mirror Mac/PC. Just as PC hardware quickly became much cheaper than Macs, Android phones will soon be significantly cheaper than an equivalent iphone. And more manufacturers will push the envelope faster than Apple will be able to, so Android will evolve faster. Cheaper and more features equates to substantially more sales - ten to one if Mac/PC history repeats itself.</p><p>Now I don't know about this guy, but most developers will judge the increased complexity of developing for multiple Android devices a small price to pay for access to a much larger marketplace.</p></htmltext>
<tokenext>If we cast our minds back twenty years , the same choice faced developers - did you make apps for the nice stable hardware-controlled Mac , or for the chaotic IBM PC compatible world ? Two points : first , it 's an amazing reflection on Apple 's success that they are a player in both of these choices.Second , I think the relative success of iphone/android will mirror Mac/PC .
Just as PC hardware quickly became much cheaper than Macs , Android phones will soon be significantly cheaper than an equivalent iphone .
And more manufacturers will push the envelope faster than Apple will be able to , so Android will evolve faster .
Cheaper and more features equates to substantially more sales - ten to one if Mac/PC history repeats itself.Now I do n't know about this guy , but most developers will judge the increased complexity of developing for multiple Android devices a small price to pay for access to a much larger marketplace .</tokentext>
<sentencetext>If we cast our minds back twenty years, the same choice faced developers - did you make apps for the nice stable hardware-controlled Mac, or for the chaotic IBM PC compatible world?Two points: first, it's an amazing reflection on Apple's success that they are a player in both of these choices.Second, I think the relative success of iphone/android will mirror Mac/PC.
Just as PC hardware quickly became much cheaper than Macs, Android phones will soon be significantly cheaper than an equivalent iphone.
And more manufacturers will push the envelope faster than Apple will be able to, so Android will evolve faster.
Cheaper and more features equates to substantially more sales - ten to one if Mac/PC history repeats itself.Now I don't know about this guy, but most developers will judge the increased complexity of developing for multiple Android devices a small price to pay for access to a much larger marketplace.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737876</id>
	<title>Re:What?</title>
	<author>Anonymous</author>
	<datestamp>1263314880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Um.... that's already happened, My phone is still 1.6, the droid is 2.0 and the N1. is 2.1.    Which version are you developing for?</p></htmltext>
<tokenext>Um.... that 's already happened , My phone is still 1.6 , the droid is 2.0 and the N1 .
is 2.1 .
Which version are you developing for ?</tokentext>
<sentencetext>Um.... that's already happened, My phone is still 1.6, the droid is 2.0 and the N1.
is 2.1.
Which version are you developing for?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737694</id>
	<title>Re:Unix way</title>
	<author>Anonymous</author>
	<datestamp>1263314220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p> <i>How does Android protect against a rouge app stealing my Google contacts</i> </p><p>It uses a turquoise filter.</p></htmltext>
<tokenext>How does Android protect against a rouge app stealing my Google contacts It uses a turquoise filter .</tokentext>
<sentencetext> How does Android protect against a rouge app stealing my Google contacts It uses a turquoise filter.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737218</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736074</id>
	<title>Re:What?</title>
	<author>happy\_place</author>
	<datestamp>1263306420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yeah, this article is as much a critique as the guy who answers the job interview question "Name your biggest weakness" as "I love my work too much, and will dedicate all my time to it, and often will work long weekends because I just can't help loving work so much."</htmltext>
<tokenext>Yeah , this article is as much a critique as the guy who answers the job interview question " Name your biggest weakness " as " I love my work too much , and will dedicate all my time to it , and often will work long weekends because I just ca n't help loving work so much .
"</tokentext>
<sentencetext>Yeah, this article is as much a critique as the guy who answers the job interview question "Name your biggest weakness" as "I love my work too much, and will dedicate all my time to it, and often will work long weekends because I just can't help loving work so much.
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30759946</id>
	<title>Re:What?</title>
	<author>HR</author>
	<datestamp>1263395580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I thought his most significant complaint was the one about the completely different programming model using intents -- the way the programs are modularized with control passing between them during execution during different lifecycle states. </p><p>Dealing with varying resolutions is kind of a pain but standard stuff on the PC. And if you want to be portable you can target the least common denominator of hardware components. But when one platform is so different in the way the program operates, it makes it very hard to have a common codebase among all the platforms you want to target.</p></htmltext>
<tokenext>I thought his most significant complaint was the one about the completely different programming model using intents -- the way the programs are modularized with control passing between them during execution during different lifecycle states .
Dealing with varying resolutions is kind of a pain but standard stuff on the PC .
And if you want to be portable you can target the least common denominator of hardware components .
But when one platform is so different in the way the program operates , it makes it very hard to have a common codebase among all the platforms you want to target .</tokentext>
<sentencetext>I thought his most significant complaint was the one about the completely different programming model using intents -- the way the programs are modularized with control passing between them during execution during different lifecycle states.
Dealing with varying resolutions is kind of a pain but standard stuff on the PC.
And if you want to be portable you can target the least common denominator of hardware components.
But when one platform is so different in the way the program operates, it makes it very hard to have a common codebase among all the platforms you want to target.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737098</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746528</id>
	<title>Re:Take if from an Android Dev</title>
	<author>ppanon</author>
	<datestamp>1263312540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Huge on the list should be the inability of Android to run apps from the SD card</p></div></blockquote><p>
Mebbe so. But that also shuts down a significant vector for viral malware and worms since SD cards are going to be one of the main physical vectors for data exchange. If you're not going to have a locked down phone which checks centrally signed code signatures, this feature is pretty important to limit malware attack vectors.</p></div>
	</htmltext>
<tokenext>Huge on the list should be the inability of Android to run apps from the SD card Mebbe so .
But that also shuts down a significant vector for viral malware and worms since SD cards are going to be one of the main physical vectors for data exchange .
If you 're not going to have a locked down phone which checks centrally signed code signatures , this feature is pretty important to limit malware attack vectors .</tokentext>
<sentencetext>Huge on the list should be the inability of Android to run apps from the SD card
Mebbe so.
But that also shuts down a significant vector for viral malware and worms since SD cards are going to be one of the main physical vectors for data exchange.
If you're not going to have a locked down phone which checks centrally signed code signatures, this feature is pretty important to limit malware attack vectors.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738696</id>
	<title>Re:veteran mobile application developer ?</title>
	<author>Unoti</author>
	<datestamp>1263317700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>A true mobile developer demands a native C/C++ interface on mobile devices - if you want something done, more than a bouncing ball on the screen - its the preferred way. NDK under Android is a must - C/C++ isn't that bad - if you know what you are doing.</p></div></blockquote><p>
Really?  Perhaps this is true if you're selling to a market where it's easy to control what kinds of devices the users will use-- say, warehouses or something, where the users are buying hardware for run your software.  But for applications you intend to sell on the app marketplace, you use C++?  Doesn't that mean you need to compile different versions for specific hardware platforms?  I'm not saying you're wrong, I'm just interested in knowing how the real pros that know what they're doing do.  Can you show me an app on the app store that's been developed in C++?</p></div>
	</htmltext>
<tokenext>A true mobile developer demands a native C/C + + interface on mobile devices - if you want something done , more than a bouncing ball on the screen - its the preferred way .
NDK under Android is a must - C/C + + is n't that bad - if you know what you are doing .
Really ? Perhaps this is true if you 're selling to a market where it 's easy to control what kinds of devices the users will use-- say , warehouses or something , where the users are buying hardware for run your software .
But for applications you intend to sell on the app marketplace , you use C + + ?
Does n't that mean you need to compile different versions for specific hardware platforms ?
I 'm not saying you 're wrong , I 'm just interested in knowing how the real pros that know what they 're doing do .
Can you show me an app on the app store that 's been developed in C + + ?</tokentext>
<sentencetext>A true mobile developer demands a native C/C++ interface on mobile devices - if you want something done, more than a bouncing ball on the screen - its the preferred way.
NDK under Android is a must - C/C++ isn't that bad - if you know what you are doing.
Really?  Perhaps this is true if you're selling to a market where it's easy to control what kinds of devices the users will use-- say, warehouses or something, where the users are buying hardware for run your software.
But for applications you intend to sell on the app marketplace, you use C++?
Doesn't that mean you need to compile different versions for specific hardware platforms?
I'm not saying you're wrong, I'm just interested in knowing how the real pros that know what they're doing do.
Can you show me an app on the app store that's been developed in C++?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735934</id>
	<title>And still ...</title>
	<author>Zarf</author>
	<datestamp>1263305580000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>... even with these valid gripes I can't imagine developing on any other platform available for the cell phone. The "Intent" is an odd term but the concept it powerful. Java is a pain but it is accessible. Most of the platform complaints deal with the novel programming style Android uses. It's an event based style with an MVC-esque pattern. Very unusual. Perhaps unusual in a good way.</p></htmltext>
<tokenext>... even with these valid gripes I ca n't imagine developing on any other platform available for the cell phone .
The " Intent " is an odd term but the concept it powerful .
Java is a pain but it is accessible .
Most of the platform complaints deal with the novel programming style Android uses .
It 's an event based style with an MVC-esque pattern .
Very unusual .
Perhaps unusual in a good way .</tokentext>
<sentencetext>... even with these valid gripes I can't imagine developing on any other platform available for the cell phone.
The "Intent" is an odd term but the concept it powerful.
Java is a pain but it is accessible.
Most of the platform complaints deal with the novel programming style Android uses.
It's an event based style with an MVC-esque pattern.
Very unusual.
Perhaps unusual in a good way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737572</id>
	<title>Re:What?</title>
	<author>Skythe</author>
	<datestamp>1263313680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I think he was more looking to complement Android. It's obvious he's a supporter of the platform, voicing some things he dislikes, but threw that in to make it not-so-negative. I think it's a well written article and he raises some valid points, although i disagree with some (i.e. activities &amp; intents can be very useful).</htmltext>
<tokenext>I think he was more looking to complement Android .
It 's obvious he 's a supporter of the platform , voicing some things he dislikes , but threw that in to make it not-so-negative .
I think it 's a well written article and he raises some valid points , although i disagree with some ( i.e .
activities &amp; intents can be very useful ) .</tokentext>
<sentencetext>I think he was more looking to complement Android.
It's obvious he's a supporter of the platform, voicing some things he dislikes, but threw that in to make it not-so-negative.
I think it's a well written article and he raises some valid points, although i disagree with some (i.e.
activities &amp; intents can be very useful).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992</id>
	<title>Re:What?</title>
	<author>Anonymous</author>
	<datestamp>1263306000000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>He does have one very legitimate concern, and that is that the platform can easily be forked, potentially ending up in a situation like old-style Unix, where each vendor had different incompatible versions of Unix (HPUX, AIX, etc).</p><p>That said, most of his other stuff sounded like "You're making it way too easy to use to create applications!"</p></htmltext>
<tokenext>He does have one very legitimate concern , and that is that the platform can easily be forked , potentially ending up in a situation like old-style Unix , where each vendor had different incompatible versions of Unix ( HPUX , AIX , etc ) .That said , most of his other stuff sounded like " You 're making it way too easy to use to create applications !
"</tokentext>
<sentencetext>He does have one very legitimate concern, and that is that the platform can easily be forked, potentially ending up in a situation like old-style Unix, where each vendor had different incompatible versions of Unix (HPUX, AIX, etc).That said, most of his other stuff sounded like "You're making it way too easy to use to create applications!
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743338</id>
	<title>Re:What?</title>
	<author>Pieroxy</author>
	<datestamp>1263293760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>More evidence that opensource=fewerbugs?</p></div><p>After reading the article, no it is not.</p><p><div class="quote"><p>The statement I quoted suggests the guy is an elitist.</p></div><p>You quoted the story, which almost always is a distorted and truncated view of a bit of the article. I'd refrain from making suggestions about a quote of a<nobr> <wbr></nobr>/. story.</p><p><div class="quote"><p>I'm not going to RTFA as it'll probably piss me off.</p></div><p>Sure, you're much better off with the distorted and truncated piece of info that doesn't inform you.</p><p><div class="quote"><p>No wonder Microsoft hates open source so much.</p></div><p>Huh... How did you slip MS in there?</p><p><div class="quote"><p>Is this guy primarily an MS dev?</p></div><p>Nope, it doesn't look like he is.</p></div>
	</htmltext>
<tokenext>More evidence that opensource = fewerbugs ? After reading the article , no it is not.The statement I quoted suggests the guy is an elitist.You quoted the story , which almost always is a distorted and truncated view of a bit of the article .
I 'd refrain from making suggestions about a quote of a / .
story.I 'm not going to RTFA as it 'll probably piss me off.Sure , you 're much better off with the distorted and truncated piece of info that does n't inform you.No wonder Microsoft hates open source so much.Huh... How did you slip MS in there ? Is this guy primarily an MS dev ? Nope , it does n't look like he is .</tokentext>
<sentencetext>More evidence that opensource=fewerbugs?After reading the article, no it is not.The statement I quoted suggests the guy is an elitist.You quoted the story, which almost always is a distorted and truncated view of a bit of the article.
I'd refrain from making suggestions about a quote of a /.
story.I'm not going to RTFA as it'll probably piss me off.Sure, you're much better off with the distorted and truncated piece of info that doesn't inform you.No wonder Microsoft hates open source so much.Huh... How did you slip MS in there?Is this guy primarily an MS dev?Nope, it doesn't look like he is.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736124</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735948</id>
	<title>Misses the point entirely</title>
	<author>For a Free Internet</author>
	<datestamp>1263305700000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>This guy is part of the Italian-Mexican conspiracy to use G$$Gle phone radio signals to turn Americans away from GOD and make us into demonic zomby robotes. So what if he gripes about the small stuff, the better to cover up G$$Gle's genocidal plan for world Italianizm.</p></htmltext>
<tokenext>This guy is part of the Italian-Mexican conspiracy to use G $ $ Gle phone radio signals to turn Americans away from GOD and make us into demonic zomby robotes .
So what if he gripes about the small stuff , the better to cover up G $ $ Gle 's genocidal plan for world Italianizm .</tokentext>
<sentencetext>This guy is part of the Italian-Mexican conspiracy to use G$$Gle phone radio signals to turn Americans away from GOD and make us into demonic zomby robotes.
So what if he gripes about the small stuff, the better to cover up G$$Gle's genocidal plan for world Italianizm.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736364</id>
	<title>Re:What?</title>
	<author>davek</author>
	<datestamp>1263308280000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Sounds to me that he's searching for things to have a problem with, and fully admits it.  At the very end of the article, he responds to<br>his own point 7, where he complains about the grammatical heresy of the Android programming concept of "Intents":</p><p><div class="quote"><p>Quite honestly, if my complaint about how the word 'Intent' makes for awkward grammatical constructions ranks in the top 10, I'd say the Android platform is doing pretty well for itself.</p></div><p>If "good debugging" and "poor grammar" are two of the top ten worst points about the platform, then I'd consider it quite a positive article.</p></div>
	</htmltext>
<tokenext>Sounds to me that he 's searching for things to have a problem with , and fully admits it .
At the very end of the article , he responds tohis own point 7 , where he complains about the grammatical heresy of the Android programming concept of " Intents " : Quite honestly , if my complaint about how the word 'Intent ' makes for awkward grammatical constructions ranks in the top 10 , I 'd say the Android platform is doing pretty well for itself.If " good debugging " and " poor grammar " are two of the top ten worst points about the platform , then I 'd consider it quite a positive article .</tokentext>
<sentencetext>Sounds to me that he's searching for things to have a problem with, and fully admits it.
At the very end of the article, he responds tohis own point 7, where he complains about the grammatical heresy of the Android programming concept of "Intents":Quite honestly, if my complaint about how the word 'Intent' makes for awkward grammatical constructions ranks in the top 10, I'd say the Android platform is doing pretty well for itself.If "good debugging" and "poor grammar" are two of the top ten worst points about the platform, then I'd consider it quite a positive article.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736400</id>
	<title>Re:Consider the source</title>
	<author>LighterShadeOfBlack</author>
	<datestamp>1263308520000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Wow. Would you like a little cheese to go with that RAGING INFERIORITY COMPLEX. The article is far from great but there's nothing wrong with the author giving a little information about himself in a linked bio. Nor anything particularly wrong with that bio. And if you read the article it's clear he doesn't actually hate Android.</p><p>So the article kind of sucks - take it out on the writing, don't get personal about someone you've (presumably) never even met. Oh, and maybe consider some kind of therapy.</p></htmltext>
<tokenext>Wow .
Would you like a little cheese to go with that RAGING INFERIORITY COMPLEX .
The article is far from great but there 's nothing wrong with the author giving a little information about himself in a linked bio .
Nor anything particularly wrong with that bio .
And if you read the article it 's clear he does n't actually hate Android.So the article kind of sucks - take it out on the writing , do n't get personal about someone you 've ( presumably ) never even met .
Oh , and maybe consider some kind of therapy .</tokentext>
<sentencetext>Wow.
Would you like a little cheese to go with that RAGING INFERIORITY COMPLEX.
The article is far from great but there's nothing wrong with the author giving a little information about himself in a linked bio.
Nor anything particularly wrong with that bio.
And if you read the article it's clear he doesn't actually hate Android.So the article kind of sucks - take it out on the writing, don't get personal about someone you've (presumably) never even met.
Oh, and maybe consider some kind of therapy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736186</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736536</id>
	<title>(Potential) iPhone Developer's Top 1 Gripe</title>
	<author>Comboman</author>
	<datestamp>1263309420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>1. SDK only available for Mac.</htmltext>
<tokenext>1 .
SDK only available for Mac .</tokentext>
<sentencetext>1.
SDK only available for Mac.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30742410</id>
	<title>Re:5. Developer Cooperative</title>
	<author>Yeroc</author>
	<datestamp>1263289260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Take it as a challenge.  Programmers of 70s &amp; 80s did amazing things with limited memory and CPU.  We're largely spoiled nowadays and often don't have to pay attention to memory usage or CPU usage.  Being forced to pay attention to these details will make you a better programmer in the end.</p></htmltext>
<tokenext>Take it as a challenge .
Programmers of 70s &amp; 80s did amazing things with limited memory and CPU .
We 're largely spoiled nowadays and often do n't have to pay attention to memory usage or CPU usage .
Being forced to pay attention to these details will make you a better programmer in the end .</tokentext>
<sentencetext>Take it as a challenge.
Programmers of 70s &amp; 80s did amazing things with limited memory and CPU.
We're largely spoiled nowadays and often don't have to pay attention to memory usage or CPU usage.
Being forced to pay attention to these details will make you a better programmer in the end.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30744668</id>
	<title>Re:What?</title>
	<author>hey!</author>
	<datestamp>1263300240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I know. What a wuss.</p><p>If debugging your code is *easy*  you aren't trying hard enough.</p></htmltext>
<tokenext>I know .
What a wuss.If debugging your code is * easy * you are n't trying hard enough .</tokentext>
<sentencetext>I know.
What a wuss.If debugging your code is *easy*  you aren't trying hard enough.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739978</id>
	<title>Re:why Java?</title>
	<author>Maxmin</author>
	<datestamp>1263322140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>2) You cannot build once run everywhere. Its a myth.</p></div></blockquote><p>You're confusing the language with the API.  Of course an Android app won't run on a J2ME device, because they COMPLETELY DIFFERENT APIs.  That'd be like expecting Windows ME apps to run directly on Windows 7.  But if you're writing to pure vanilla J2SE, you *CAN* write once run anywhere, given equivalent API versions.</p><blockquote><div><p>3) Java *IS* an order of magnitude slower than C/ASM for many things that are important for games, such as matrix math. Google knows this and is trying to work around it with JNI/NDK, but really why the complication?</p></div></blockquote><p>What's good about Java, and in particular Android, is the separation of high and low-level operations.  Sure, it'd be great if we all could code our apps in C or ASM, we wouldn't need Moore's Law to pull some of the beefier OSes and apps out of the swamp, now would we?  But we don't all have your programming skill level.</p><p>For games on Android, there's OpenGL ES, which provides support for both GPU and emulated GPU operations, allowing for very speedy games.</p></div>
	</htmltext>
<tokenext>2 ) You can not build once run everywhere .
Its a myth.You 're confusing the language with the API .
Of course an Android app wo n't run on a J2ME device , because they COMPLETELY DIFFERENT APIs .
That 'd be like expecting Windows ME apps to run directly on Windows 7 .
But if you 're writing to pure vanilla J2SE , you * CAN * write once run anywhere , given equivalent API versions.3 ) Java * IS * an order of magnitude slower than C/ASM for many things that are important for games , such as matrix math .
Google knows this and is trying to work around it with JNI/NDK , but really why the complication ? What 's good about Java , and in particular Android , is the separation of high and low-level operations .
Sure , it 'd be great if we all could code our apps in C or ASM , we would n't need Moore 's Law to pull some of the beefier OSes and apps out of the swamp , now would we ?
But we do n't all have your programming skill level.For games on Android , there 's OpenGL ES , which provides support for both GPU and emulated GPU operations , allowing for very speedy games .</tokentext>
<sentencetext>2) You cannot build once run everywhere.
Its a myth.You're confusing the language with the API.
Of course an Android app won't run on a J2ME device, because they COMPLETELY DIFFERENT APIs.
That'd be like expecting Windows ME apps to run directly on Windows 7.
But if you're writing to pure vanilla J2SE, you *CAN* write once run anywhere, given equivalent API versions.3) Java *IS* an order of magnitude slower than C/ASM for many things that are important for games, such as matrix math.
Google knows this and is trying to work around it with JNI/NDK, but really why the complication?What's good about Java, and in particular Android, is the separation of high and low-level operations.
Sure, it'd be great if we all could code our apps in C or ASM, we wouldn't need Moore's Law to pull some of the beefier OSes and apps out of the swamp, now would we?
But we don't all have your programming skill level.For games on Android, there's OpenGL ES, which provides support for both GPU and emulated GPU operations, allowing for very speedy games.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736850</id>
	<title>Re:why Java?</title>
	<author>fredrik70</author>
	<datestamp>1263310860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>hold your horses, Java aint *that* bad.  With the ability to write c libs for your java code I think things should be ok. Personally I prefer to do the UI in java/xml and then any heavy number crunshing in c. that way you use the languages for what they are best for. At least until someone ports QT to android phones.<nobr> <wbr></nobr>;-)<br>Also when they get the JIT to work for the Dalvik runtime things will also be a bit better</p></htmltext>
<tokenext>hold your horses , Java aint * that * bad .
With the ability to write c libs for your java code I think things should be ok. Personally I prefer to do the UI in java/xml and then any heavy number crunshing in c. that way you use the languages for what they are best for .
At least until someone ports QT to android phones .
; - ) Also when they get the JIT to work for the Dalvik runtime things will also be a bit better</tokentext>
<sentencetext>hold your horses, Java aint *that* bad.
With the ability to write c libs for your java code I think things should be ok. Personally I prefer to do the UI in java/xml and then any heavy number crunshing in c. that way you use the languages for what they are best for.
At least until someone ports QT to android phones.
;-)Also when they get the JIT to work for the Dalvik runtime things will also be a bit better</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737518</id>
	<title>Re:What?</title>
	<author>rickb928</author>
	<datestamp>1263313440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Had you read the last paragraph, you would not have found the word 'angry' to accurately describe the author's attitude towards Android.  At least not as accurate as 'favorite'.</p><p>sheesh.</p></htmltext>
<tokenext>Had you read the last paragraph , you would not have found the word 'angry ' to accurately describe the author 's attitude towards Android .
At least not as accurate as 'favorite'.sheesh .</tokentext>
<sentencetext>Had you read the last paragraph, you would not have found the word 'angry' to accurately describe the author's attitude towards Android.
At least not as accurate as 'favorite'.sheesh.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737906</id>
	<title>Re:veteran mobile application developer ?</title>
	<author>Anonymous</author>
	<datestamp>1263314940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>&gt;&gt; 8. Platform Fragmentation</p><p>its a problem? come on - seriously. you deal with it. you design around it; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues. just because most companies hire an outsourcing department or "specialists" on specific platforms isn't a problem - it is a choice. there are plenty of alternatives out there.</p></div><p>It will be a problem...<br>"Hey you have the ultimate application on your "Android" phone? Can I have it?"<br>"Sorry, I have the HTC Andydroid and you have the Moto Droidinator and it isn't compatible. There's some obscure bug that not even Google Search can find an explanation for."</p></div>
	</htmltext>
<tokenext>&gt; &gt; 8 .
Platform Fragmentationits a problem ?
come on - seriously .
you deal with it .
you design around it ; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues .
just because most companies hire an outsourcing department or " specialists " on specific platforms is n't a problem - it is a choice .
there are plenty of alternatives out there.It will be a problem... " Hey you have the ultimate application on your " Android " phone ?
Can I have it ?
" " Sorry , I have the HTC Andydroid and you have the Moto Droidinator and it is n't compatible .
There 's some obscure bug that not even Google Search can find an explanation for .
"</tokentext>
<sentencetext>&gt;&gt; 8.
Platform Fragmentationits a problem?
come on - seriously.
you deal with it.
you design around it; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues.
just because most companies hire an outsourcing department or "specialists" on specific platforms isn't a problem - it is a choice.
there are plenty of alternatives out there.It will be a problem..."Hey you have the ultimate application on your "Android" phone?
Can I have it?
""Sorry, I have the HTC Andydroid and you have the Moto Droidinator and it isn't compatible.
There's some obscure bug that not even Google Search can find an explanation for.
"
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737692</id>
	<title>Re:Unix way</title>
	<author>Rysc</author>
	<datestamp>1263314220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>ZeroInstall (aka 0install) (http://0install.net/howitworks.html)</p><p>rox filer/rox desktop (http://roscidus.com/desktop/)</p><p>nixOS (http://nixos.org/nixos/)</p><p>GoboLinux (http://www.gobolinux.org/)</p><p>If it were a *good* idea one or more of these things would be dominating by now.</p></htmltext>
<tokenext>ZeroInstall ( aka 0install ) ( http : //0install.net/howitworks.html ) rox filer/rox desktop ( http : //roscidus.com/desktop/ ) nixOS ( http : //nixos.org/nixos/ ) GoboLinux ( http : //www.gobolinux.org/ ) If it were a * good * idea one or more of these things would be dominating by now .</tokentext>
<sentencetext>ZeroInstall (aka 0install) (http://0install.net/howitworks.html)rox filer/rox desktop (http://roscidus.com/desktop/)nixOS (http://nixos.org/nixos/)GoboLinux (http://www.gobolinux.org/)If it were a *good* idea one or more of these things would be dominating by now.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740168</id>
	<title>Re:What?</title>
	<author>Zorkon</author>
	<datestamp>1263322920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Have you done any Android development work? I have, and I can say that it's more likely that Activities &amp; Intents have fueled his rage. The debugging thing was just the kindling that got the fire started.</p></htmltext>
<tokenext>Have you done any Android development work ?
I have , and I can say that it 's more likely that Activities &amp; Intents have fueled his rage .
The debugging thing was just the kindling that got the fire started .</tokentext>
<sentencetext>Have you done any Android development work?
I have, and I can say that it's more likely that Activities &amp; Intents have fueled his rage.
The debugging thing was just the kindling that got the fire started.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736446</id>
	<title>Re:dumb article/crappy developer</title>
	<author>numbski</author>
	<datestamp>1263308940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Point 5 seems simple enough - no tyranny required.</p><p>Nice the application in the foreground to have high priority, renice everything not in the foreground behind it.  Problem averted.</p><p>Am I missing something?  I know that doesn't address RAM, but if one wanted to, they could load a small memory management daemon that matches RAM/swap use to the current nice states.  Whatever is in the foreground can have physical memory, everything else goes to swap unless physical happens to be free and not in use.</p></htmltext>
<tokenext>Point 5 seems simple enough - no tyranny required.Nice the application in the foreground to have high priority , renice everything not in the foreground behind it .
Problem averted.Am I missing something ?
I know that does n't address RAM , but if one wanted to , they could load a small memory management daemon that matches RAM/swap use to the current nice states .
Whatever is in the foreground can have physical memory , everything else goes to swap unless physical happens to be free and not in use .</tokentext>
<sentencetext>Point 5 seems simple enough - no tyranny required.Nice the application in the foreground to have high priority, renice everything not in the foreground behind it.
Problem averted.Am I missing something?
I know that doesn't address RAM, but if one wanted to, they could load a small memory management daemon that matches RAM/swap use to the current nice states.
Whatever is in the foreground can have physical memory, everything else goes to swap unless physical happens to be free and not in use.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746066</id>
	<title>It worked for me!</title>
	<author>hedronist</author>
	<datestamp>1263308520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
<i>He does have one very legitimate concern, and that is that the platform can easily be forked, potentially ending up in a situation like old-style Unix, where each vendor had different incompatible versions of Unix (HPUX, AIX, etc).
</i>

</p><p>
I happened to write the first source-level C debugger that actually worked (sdb was buggy as hell, and dbx at Sun was debugged with my debugger). I absolutely <i>loved</i> it when the <i>Yates Report</i> would say that yet another company would "capture 20\% of the UNIX market." I waltzed on over, gave their senior geeks a pitch, and waited for the manager fold as they begged for a working debugger.
</p><p>
I say, "The more forks the merrier!"</p></htmltext>
<tokenext>He does have one very legitimate concern , and that is that the platform can easily be forked , potentially ending up in a situation like old-style Unix , where each vendor had different incompatible versions of Unix ( HPUX , AIX , etc ) .
I happened to write the first source-level C debugger that actually worked ( sdb was buggy as hell , and dbx at Sun was debugged with my debugger ) .
I absolutely loved it when the Yates Report would say that yet another company would " capture 20 \ % of the UNIX market .
" I waltzed on over , gave their senior geeks a pitch , and waited for the manager fold as they begged for a working debugger .
I say , " The more forks the merrier !
"</tokentext>
<sentencetext>
He does have one very legitimate concern, and that is that the platform can easily be forked, potentially ending up in a situation like old-style Unix, where each vendor had different incompatible versions of Unix (HPUX, AIX, etc).
I happened to write the first source-level C debugger that actually worked (sdb was buggy as hell, and dbx at Sun was debugged with my debugger).
I absolutely loved it when the Yates Report would say that yet another company would "capture 20\% of the UNIX market.
" I waltzed on over, gave their senior geeks a pitch, and waited for the manager fold as they begged for a working debugger.
I say, "The more forks the merrier!
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736188</id>
	<title>Debug on the Underdog</title>
	<author>Anonymous</author>
	<datestamp>1263307140000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>Hey, I've been debugging for years on Windows Mobile...so, what's the story?</p></htmltext>
<tokenext>Hey , I 've been debugging for years on Windows Mobile...so , what 's the story ?</tokentext>
<sentencetext>Hey, I've been debugging for years on Windows Mobile...so, what's the story?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737396</id>
	<title>Your books sales... down!</title>
	<author>Anonymous</author>
	<datestamp>1263312900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What the hell are you talking about?  Open source a bad thing?!?!  That means more apps and more... so much more to choose from.

New and great debugging tools a bad thing!?!! What!  That's like saying you love to write large webpages in notepad.  Time is money mate!  As an independent developer you should know that.

I didn't read anything other than what I commented on above.  This article was so sad.

In conclusion I think this dudes blowing of steam because Google just made his book useless.</htmltext>
<tokenext>What the hell are you talking about ?
Open source a bad thing ? ! ? !
That means more apps and more... so much more to choose from .
New and great debugging tools a bad thing ! ? ! !
What ! That 's like saying you love to write large webpages in notepad .
Time is money mate !
As an independent developer you should know that .
I did n't read anything other than what I commented on above .
This article was so sad .
In conclusion I think this dudes blowing of steam because Google just made his book useless .</tokentext>
<sentencetext>What the hell are you talking about?
Open source a bad thing?!?!
That means more apps and more... so much more to choose from.
New and great debugging tools a bad thing!?!!
What!  That's like saying you love to write large webpages in notepad.
Time is money mate!
As an independent developer you should know that.
I didn't read anything other than what I commented on above.
This article was so sad.
In conclusion I think this dudes blowing of steam because Google just made his book useless.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739414</id>
	<title>self-deprecating points in TFA and the parent</title>
	<author>roman\_mir</author>
	<datestamp>1263320100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This:</p><p><div class="quote"><p>&gt;&gt; 6. Java--Thanks, But I'll Take It from Here</p><p>Java - probably the worst language used on mobile devices to date.</p></div><p>and this:</p><p><div class="quote"><p>&gt;&gt; 8. Platform Fragmentation</p><p>its a problem? come on - seriously. you deal with it. you design around it; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues.</p></div><p>Java is the answer to platform fragmentation.</p></div>
	</htmltext>
<tokenext>This : &gt; &gt; 6 .
Java--Thanks , But I 'll Take It from HereJava - probably the worst language used on mobile devices to date.and this : &gt; &gt; 8 .
Platform Fragmentationits a problem ?
come on - seriously .
you deal with it .
you design around it ; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues.Java is the answer to platform fragmentation .</tokentext>
<sentencetext>This:&gt;&gt; 6.
Java--Thanks, But I'll Take It from HereJava - probably the worst language used on mobile devices to date.and this:&gt;&gt; 8.
Platform Fragmentationits a problem?
come on - seriously.
you deal with it.
you design around it; thats where your years of experience really kicks in and allows you to build cross-platform applications without issues.Java is the answer to platform fragmentation.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738382</id>
	<title>Re:What?</title>
	<author>rliden</author>
	<datestamp>1263316620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's the point of open source though isn't it?  Any developer, company, etc can take the code modify it for it's own use and distribute it within the license agreement.  Maybe the answer to ensuring cross brand compatibility with applications is for Google to develop a standard interface that requires third party system developers to implement in order to use the Google or Droid trademark on the phone.</p></htmltext>
<tokenext>That 's the point of open source though is n't it ?
Any developer , company , etc can take the code modify it for it 's own use and distribute it within the license agreement .
Maybe the answer to ensuring cross brand compatibility with applications is for Google to develop a standard interface that requires third party system developers to implement in order to use the Google or Droid trademark on the phone .</tokentext>
<sentencetext>That's the point of open source though isn't it?
Any developer, company, etc can take the code modify it for it's own use and distribute it within the license agreement.
Maybe the answer to ensuring cross brand compatibility with applications is for Google to develop a standard interface that requires third party system developers to implement in order to use the Google or Droid trademark on the phone.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30744574</id>
	<title>Re:veteran mobile application developer ?</title>
	<author>DissociativeBehavior</author>
	<datestamp>1263299760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>A true mobile developer demands a native C/C++ interface on mobile devices</p></div><p>
A C/C++ interface requires an OS supporting virtual memory and exception handling. Many low and middle end phones only have a simple real time OS with a flat memory space, and no exception support. A memory access violation usually results in a reset.
</p><p>
One of the advantage of a Java VM is that it requires minimal support from the OS and implements all the security required to isolate the application from the rest of the software.
</p><p>
Plus on modern implementations, the java code is almost equivalent to native code:
- the most frequently used methods are compiled on the fly
- the critical APIs are declared native, meaning they are written in C and not in java.</p></div>
	</htmltext>
<tokenext>A true mobile developer demands a native C/C + + interface on mobile devices A C/C + + interface requires an OS supporting virtual memory and exception handling .
Many low and middle end phones only have a simple real time OS with a flat memory space , and no exception support .
A memory access violation usually results in a reset .
One of the advantage of a Java VM is that it requires minimal support from the OS and implements all the security required to isolate the application from the rest of the software .
Plus on modern implementations , the java code is almost equivalent to native code : - the most frequently used methods are compiled on the fly - the critical APIs are declared native , meaning they are written in C and not in java .</tokentext>
<sentencetext>A true mobile developer demands a native C/C++ interface on mobile devices
A C/C++ interface requires an OS supporting virtual memory and exception handling.
Many low and middle end phones only have a simple real time OS with a flat memory space, and no exception support.
A memory access violation usually results in a reset.
One of the advantage of a Java VM is that it requires minimal support from the OS and implements all the security required to isolate the application from the rest of the software.
Plus on modern implementations, the java code is almost equivalent to native code:
- the most frequently used methods are compiled on the fly
- the critical APIs are declared native, meaning they are written in C and not in java.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736132</id>
	<title>Who says Google talks clearly?</title>
	<author>jonaskoelker</author>
	<datestamp>1263306780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Actually, that's quite simple. It's ok when Google (the copyright holder) says it's ok, otherwise it's not.</p></div><p>Agreed.  Understanding what Google actually says might not be so simple, though.  I think that's why people have a tendency to employ people* who are experts at interpreting law and contracts.</p><p>(*) I mean lawyers.</p></div>
	</htmltext>
<tokenext>Actually , that 's quite simple .
It 's ok when Google ( the copyright holder ) says it 's ok , otherwise it 's not.Agreed .
Understanding what Google actually says might not be so simple , though .
I think that 's why people have a tendency to employ people * who are experts at interpreting law and contracts .
( * ) I mean lawyers .</tokentext>
<sentencetext>Actually, that's quite simple.
It's ok when Google (the copyright holder) says it's ok, otherwise it's not.Agreed.
Understanding what Google actually says might not be so simple, though.
I think that's why people have a tendency to employ people* who are experts at interpreting law and contracts.
(*) I mean lawyers.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30745878
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737098
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740654
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737266
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737692
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736400
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736186
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743338
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736124
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737134
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30744574
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737788
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737418
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743882
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736784
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736306
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30742410
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740534
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736234
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739978
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746066
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740168
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736594
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738176
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746154
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735934
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740046
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737694
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737218
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736350
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739176
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746528
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736364
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736614
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737906
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736636
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737896
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737158
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743676
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30759946
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737098
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739652
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738382
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736814
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30744668
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737076
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738590
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736446
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738696
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738720
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736420
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736850
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737518
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737796
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735934
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736074
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736706
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739414
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736270
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736056
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736132
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736612
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736186
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_12_001207_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737014
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736234
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736026
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736446
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738590
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736132
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736270
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736992
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736420
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736394
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737158
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736706
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737266
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740654
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736234
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740534
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737014
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736674
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736540
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737134
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738176
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736850
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739978
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737396
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735930
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736350
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737218
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737694
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736366
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739176
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737692
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736636
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736614
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735916
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737076
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738720
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737896
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736124
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743338
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736056
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737518
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735992
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746066
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739652
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737876
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738382
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736306
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737098
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30759946
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30745878
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737788
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740168
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736594
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736074
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737572
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30744668
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737418
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736364
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30741342
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737288
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30740046
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743676
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30742410
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739592
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736550
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746528
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736188
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736162
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30738696
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30744574
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30739414
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737906
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736814
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736186
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736612
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736400
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30735934
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30746154
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30737796
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736536
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_12_001207.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30736784
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_12_001207.30743882
</commentlist>
</conversation>
