<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_03_10_192224</id>
	<title>6 Smartphone Keyboards Compared</title>
	<author>timothy</author>
	<datestamp>1268249700000</datestamp>
	<htmltext>Barence writes <i>"A debate that crops up time and again is whether it's better to have a dedicated keyboard on your smartphone or whether an on-screen keyboard with text correction is adequate. Some phones with screen-based keyboards have started to provide tactile feedback, either using an ultra-quick spin of their vibration alert or, like the BlackBerry Storm2, using clever piezo-electric technology to simulate the feel of a button press. But which system works best? PC Pro's Paul Ockendon gathered six of the most popular handsets around and put them through a <a href="http://www.pcpro.co.uk/realworld/356233/which-smartphone-keyboard-is-the-best">timed typing test to see which proved quickest and most typo-free</a>."</i></htmltext>
<tokenext>Barence writes " A debate that crops up time and again is whether it 's better to have a dedicated keyboard on your smartphone or whether an on-screen keyboard with text correction is adequate .
Some phones with screen-based keyboards have started to provide tactile feedback , either using an ultra-quick spin of their vibration alert or , like the BlackBerry Storm2 , using clever piezo-electric technology to simulate the feel of a button press .
But which system works best ?
PC Pro 's Paul Ockendon gathered six of the most popular handsets around and put them through a timed typing test to see which proved quickest and most typo-free .
"</tokentext>
<sentencetext>Barence writes "A debate that crops up time and again is whether it's better to have a dedicated keyboard on your smartphone or whether an on-screen keyboard with text correction is adequate.
Some phones with screen-based keyboards have started to provide tactile feedback, either using an ultra-quick spin of their vibration alert or, like the BlackBerry Storm2, using clever piezo-electric technology to simulate the feel of a button press.
But which system works best?
PC Pro's Paul Ockendon gathered six of the most popular handsets around and put them through a timed typing test to see which proved quickest and most typo-free.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431118</id>
	<title>What a waste of time</title>
	<author>Targon</author>
	<datestamp>1268216340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So, the author decides to post about experiences with those six devices, leaving out MANY other devices.    The old Palm Treo is very dated at this point, but still good for comparison purposes.   How about the Palm Pre, or any of the other lesser known phones that have a keyboard?    You may as well just go into your local hardware store and compare surge protectors and then claim it is news, without mentioning that a hardware store isn't going to give enough of a selection to make any sort of comparison meaningful.</p></htmltext>
<tokenext>So , the author decides to post about experiences with those six devices , leaving out MANY other devices .
The old Palm Treo is very dated at this point , but still good for comparison purposes .
How about the Palm Pre , or any of the other lesser known phones that have a keyboard ?
You may as well just go into your local hardware store and compare surge protectors and then claim it is news , without mentioning that a hardware store is n't going to give enough of a selection to make any sort of comparison meaningful .</tokentext>
<sentencetext>So, the author decides to post about experiences with those six devices, leaving out MANY other devices.
The old Palm Treo is very dated at this point, but still good for comparison purposes.
How about the Palm Pre, or any of the other lesser known phones that have a keyboard?
You may as well just go into your local hardware store and compare surge protectors and then claim it is news, without mentioning that a hardware store isn't going to give enough of a selection to make any sort of comparison meaningful.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430272</id>
	<title>HTC Dream AKA G1</title>
	<author>Audax\_23</author>
	<datestamp>1268212320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'm very curious how the G1 (HTC Dream) would have compared.  The CPU, memory and screen specs are looking a little dated, but from my (albiet limited) observation, the physical keyboard still seem to be a top notch contender.  Particularly because of the innate tactile feedback, due to fairly clicky keys, and the perhaps somewhat overlooked factor of the keys being laid out in the standard diagonal orientation, which I've definitely found to be quite advantageous. <br>

<br>

I'm not the worlds fastest typist, but I can touch type, and when I began using that phone, the ability to do so seamlessly transferred to that hardware.  Which was interesting since completely different digits are involved.  (thumbs vs fingers). <br>

<br>

Am convinced that the speed bottleneck involved in on-screen keyboards is more due to do placing the users visual system inside the control feedback loop, which is inherently slower and consumes more resources.</htmltext>
<tokenext>I 'm very curious how the G1 ( HTC Dream ) would have compared .
The CPU , memory and screen specs are looking a little dated , but from my ( albiet limited ) observation , the physical keyboard still seem to be a top notch contender .
Particularly because of the innate tactile feedback , due to fairly clicky keys , and the perhaps somewhat overlooked factor of the keys being laid out in the standard diagonal orientation , which I 've definitely found to be quite advantageous .
I 'm not the worlds fastest typist , but I can touch type , and when I began using that phone , the ability to do so seamlessly transferred to that hardware .
Which was interesting since completely different digits are involved .
( thumbs vs fingers ) .
Am convinced that the speed bottleneck involved in on-screen keyboards is more due to do placing the users visual system inside the control feedback loop , which is inherently slower and consumes more resources .</tokentext>
<sentencetext>I'm very curious how the G1 (HTC Dream) would have compared.
The CPU, memory and screen specs are looking a little dated, but from my (albiet limited) observation, the physical keyboard still seem to be a top notch contender.
Particularly because of the innate tactile feedback, due to fairly clicky keys, and the perhaps somewhat overlooked factor of the keys being laid out in the standard diagonal orientation, which I've definitely found to be quite advantageous.
I'm not the worlds fastest typist, but I can touch type, and when I began using that phone, the ability to do so seamlessly transferred to that hardware.
Which was interesting since completely different digits are involved.
(thumbs vs fingers).
Am convinced that the speed bottleneck involved in on-screen keyboards is more due to do placing the users visual system inside the control feedback loop, which is inherently slower and consumes more resources.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31456742</id>
	<title>Touch is best in my experience</title>
	<author>Anonymous</author>
	<datestamp>1268389260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>After 18 months with an iPhone type at around 30 words per minute. The auto correct fixes typos in every tenth word or so, giving near perfect accuracy. It's nothing compared to the 100 wpm I get on a PC keyboard, but definitely good enough (I'm writing this on it).</p><p>Lately I've started "touch" typing, where I look at the words rather than the keys.</p><p>When I pick up my gf's nokia with a hardware, I'm screwed. I can barely type at all... I can't seem to get out of the habit of touching the keys without physical force.</p><p>For me, it not even a matter of feel, I don't want to have to push a key, a light tap feels much faster. I even wonder if I could beat my 100 wpm on conventional keyboards with a touch surface big enough to use 10 fingers.</p></htmltext>
<tokenext>After 18 months with an iPhone type at around 30 words per minute .
The auto correct fixes typos in every tenth word or so , giving near perfect accuracy .
It 's nothing compared to the 100 wpm I get on a PC keyboard , but definitely good enough ( I 'm writing this on it ) .Lately I 've started " touch " typing , where I look at the words rather than the keys.When I pick up my gf 's nokia with a hardware , I 'm screwed .
I can barely type at all... I ca n't seem to get out of the habit of touching the keys without physical force.For me , it not even a matter of feel , I do n't want to have to push a key , a light tap feels much faster .
I even wonder if I could beat my 100 wpm on conventional keyboards with a touch surface big enough to use 10 fingers .</tokentext>
<sentencetext>After 18 months with an iPhone type at around 30 words per minute.
The auto correct fixes typos in every tenth word or so, giving near perfect accuracy.
It's nothing compared to the 100 wpm I get on a PC keyboard, but definitely good enough (I'm writing this on it).Lately I've started "touch" typing, where I look at the words rather than the keys.When I pick up my gf's nokia with a hardware, I'm screwed.
I can barely type at all... I can't seem to get out of the habit of touching the keys without physical force.For me, it not even a matter of feel, I don't want to have to push a key, a light tap feels much faster.
I even wonder if I could beat my 100 wpm on conventional keyboards with a touch surface big enough to use 10 fingers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31434656</id>
	<title>Re:Bias? and the training effect</title>
	<author>brisvegasdan</author>
	<datestamp>1268244120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>never mind the learning effect of typing the same phrase multiple times, it normally favours the later trials so maybe a baseline offset is required and the last phone might come in a bit slower than thought. Of course to be truly scientific he should have worn two blind folds? FWIW anyone debunking evidence based research would do well to participate in a double blind crossover trial of efficacy of parachutes since they have never been proven to be effective through the use of a control group<nobr> <wbr></nobr>;)</htmltext>
<tokenext>never mind the learning effect of typing the same phrase multiple times , it normally favours the later trials so maybe a baseline offset is required and the last phone might come in a bit slower than thought .
Of course to be truly scientific he should have worn two blind folds ?
FWIW anyone debunking evidence based research would do well to participate in a double blind crossover trial of efficacy of parachutes since they have never been proven to be effective through the use of a control group ; )</tokentext>
<sentencetext>never mind the learning effect of typing the same phrase multiple times, it normally favours the later trials so maybe a baseline offset is required and the last phone might come in a bit slower than thought.
Of course to be truly scientific he should have worn two blind folds?
FWIW anyone debunking evidence based research would do well to participate in a double blind crossover trial of efficacy of parachutes since they have never been proven to be effective through the use of a control group ;)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430252</id>
	<title>physical keyboard ==</title>
	<author>jsnipy</author>
	<datestamp>1268212260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>more screen space</htmltext>
<tokenext>more screen space</tokentext>
<sentencetext>more screen space</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431110</id>
	<title>alternative keypad design</title>
	<author>gibson123</author>
	<datestamp>1268216280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I have followed this company for sometime, with a novel keypad idea:
<a href="http://www.digitwireless.com/" title="digitwireless.com" rel="nofollow">http://www.digitwireless.com/</a> [digitwireless.com]  I have yet to see it in the marketplace though.  I once spoke to the inventor who holds the patent.</htmltext>
<tokenext>I have followed this company for sometime , with a novel keypad idea : http : //www.digitwireless.com/ [ digitwireless.com ] I have yet to see it in the marketplace though .
I once spoke to the inventor who holds the patent .</tokentext>
<sentencetext>I have followed this company for sometime, with a novel keypad idea:
http://www.digitwireless.com/ [digitwireless.com]  I have yet to see it in the marketplace though.
I once spoke to the inventor who holds the patent.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431322</id>
	<title>I like a physical KB, but...</title>
	<author>toadlife</author>
	<datestamp>1268217360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>As someone who has never owned an iphone, I never understood why iphone users raved so much about their on-screen keyboards, until I got my current phone. My previous phones were the Blackbery Pearl and then the t-mobile wing. The Pearl of course has no touch screen and the Wing's screen was too small and the hardware too underpowered to make a decent on-screen keyboard feasible. My current phone,  the touch pro 2, has the finger friendly on-screen keyboard and on-the-fly error correction that the iphone has had since it's inception and I've come to really enjoy it for typing emails and notes. I still value the slide out keyboard for tasks that require numbers and symbols though. The T-Mobile version of the Touch Pro 2 has a dedicated number row at the top, which is incredibly useful and, IMO, makes it superior to other versions of the Touch Pro 2.</p></htmltext>
<tokenext>As someone who has never owned an iphone , I never understood why iphone users raved so much about their on-screen keyboards , until I got my current phone .
My previous phones were the Blackbery Pearl and then the t-mobile wing .
The Pearl of course has no touch screen and the Wing 's screen was too small and the hardware too underpowered to make a decent on-screen keyboard feasible .
My current phone , the touch pro 2 , has the finger friendly on-screen keyboard and on-the-fly error correction that the iphone has had since it 's inception and I 've come to really enjoy it for typing emails and notes .
I still value the slide out keyboard for tasks that require numbers and symbols though .
The T-Mobile version of the Touch Pro 2 has a dedicated number row at the top , which is incredibly useful and , IMO , makes it superior to other versions of the Touch Pro 2 .</tokentext>
<sentencetext>As someone who has never owned an iphone, I never understood why iphone users raved so much about their on-screen keyboards, until I got my current phone.
My previous phones were the Blackbery Pearl and then the t-mobile wing.
The Pearl of course has no touch screen and the Wing's screen was too small and the hardware too underpowered to make a decent on-screen keyboard feasible.
My current phone,  the touch pro 2, has the finger friendly on-screen keyboard and on-the-fly error correction that the iphone has had since it's inception and I've come to really enjoy it for typing emails and notes.
I still value the slide out keyboard for tasks that require numbers and symbols though.
The T-Mobile version of the Touch Pro 2 has a dedicated number row at the top, which is incredibly useful and, IMO, makes it superior to other versions of the Touch Pro 2.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432572</id>
	<title>Re:Blackberry</title>
	<author>kosh</author>
	<datestamp>1268224140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"The Fingers You Have Used to dial Are Too Fat. to obtain a Special Dialing Wand, Please Mash the Keypad with Your Palm Now."</p></htmltext>
<tokenext>" The Fingers You Have Used to dial Are Too Fat .
to obtain a Special Dialing Wand , Please Mash the Keypad with Your Palm Now .
"</tokentext>
<sentencetext>"The Fingers You Have Used to dial Are Too Fat.
to obtain a Special Dialing Wand, Please Mash the Keypad with Your Palm Now.
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429910</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429880</id>
	<title>Subjective somewhat?</title>
	<author>Anonymous</author>
	<datestamp>1268253720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Depending on what you're used to on existing devices and who is typing, these results will vary wildly. I'm used to a physical keyboard on my phone so I have trouble whenever I try to use something else. I tried tactile feedback screens once and the vibrations felt funny making me go even slower.</p><p>I've got a really flat, sensitive keyboard with repeat all the way up and key delay all the way down and a trackball mouse. Most people that try to type on it or use my mouse can't because the keyboard is too sensitive and they don't know what to do with the mouse (some try to move the whole unit, some just look at it and seem to poke at it). I however can type faster on it than any other keyboard and be precise in even difficult 3D shooters.</p><p>These 'tests' really require a decent sample size of users and a decent sample size of devices with said screens. Not everybody implements the on-screen keyboard in the same way either.</p></htmltext>
<tokenext>Depending on what you 're used to on existing devices and who is typing , these results will vary wildly .
I 'm used to a physical keyboard on my phone so I have trouble whenever I try to use something else .
I tried tactile feedback screens once and the vibrations felt funny making me go even slower.I 've got a really flat , sensitive keyboard with repeat all the way up and key delay all the way down and a trackball mouse .
Most people that try to type on it or use my mouse ca n't because the keyboard is too sensitive and they do n't know what to do with the mouse ( some try to move the whole unit , some just look at it and seem to poke at it ) .
I however can type faster on it than any other keyboard and be precise in even difficult 3D shooters.These 'tests ' really require a decent sample size of users and a decent sample size of devices with said screens .
Not everybody implements the on-screen keyboard in the same way either .</tokentext>
<sentencetext>Depending on what you're used to on existing devices and who is typing, these results will vary wildly.
I'm used to a physical keyboard on my phone so I have trouble whenever I try to use something else.
I tried tactile feedback screens once and the vibrations felt funny making me go even slower.I've got a really flat, sensitive keyboard with repeat all the way up and key delay all the way down and a trackball mouse.
Most people that try to type on it or use my mouse can't because the keyboard is too sensitive and they don't know what to do with the mouse (some try to move the whole unit, some just look at it and seem to poke at it).
I however can type faster on it than any other keyboard and be precise in even difficult 3D shooters.These 'tests' really require a decent sample size of users and a decent sample size of devices with said screens.
Not everybody implements the on-screen keyboard in the same way either.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806</id>
	<title>Debate</title>
	<author>Anonymous</author>
	<datestamp>1268253480000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>What debate? You're telling me that there are people who seriously prefer to *not* have a physical keyboard on their smartphone?</p></htmltext>
<tokenext>What debate ?
You 're telling me that there are people who seriously prefer to * not * have a physical keyboard on their smartphone ?</tokentext>
<sentencetext>What debate?
You're telling me that there are people who seriously prefer to *not* have a physical keyboard on their smartphone?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429964</id>
	<title>Of course.. they left out the original and best</title>
	<author>Anonymous</author>
	<datestamp>1268254080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>They didn't even include any Palm products in their review.. and Palm, being both the original smartphone, and the best (at least in my opinion), deserved to be included.<br>The crapberry bold that "won" has an imitation of the keyboard on a Palm Treo 680 and similar.. the Pre has a similar keyboard as well.. probably further refined than the one RIM ripped-off for the crapberry bold.</p><p>I wonder just where RIM's money comes into the equation of paying the person who wrote the review to pan everyone else's product.. while being sure to mention one OTHER crapberry in order not to look biased.</p></htmltext>
<tokenext>They did n't even include any Palm products in their review.. and Palm , being both the original smartphone , and the best ( at least in my opinion ) , deserved to be included.The crapberry bold that " won " has an imitation of the keyboard on a Palm Treo 680 and similar.. the Pre has a similar keyboard as well.. probably further refined than the one RIM ripped-off for the crapberry bold.I wonder just where RIM 's money comes into the equation of paying the person who wrote the review to pan everyone else 's product.. while being sure to mention one OTHER crapberry in order not to look biased .</tokentext>
<sentencetext>They didn't even include any Palm products in their review.. and Palm, being both the original smartphone, and the best (at least in my opinion), deserved to be included.The crapberry bold that "won" has an imitation of the keyboard on a Palm Treo 680 and similar.. the Pre has a similar keyboard as well.. probably further refined than the one RIM ripped-off for the crapberry bold.I wonder just where RIM's money comes into the equation of paying the person who wrote the review to pan everyone else's product.. while being sure to mention one OTHER crapberry in order not to look biased.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31434052</id>
	<title>Regrettably...</title>
	<author>Anonymous</author>
	<datestamp>1268237040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Regrettably, the best keyboard I've used on a Smartphone was on a Danger Sidekick, by far.</p></htmltext>
<tokenext>Regrettably , the best keyboard I 've used on a Smartphone was on a Danger Sidekick , by far .</tokentext>
<sentencetext>Regrettably, the best keyboard I've used on a Smartphone was on a Danger Sidekick, by far.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429954</id>
	<title>YMMV</title>
	<author>gmuslera</author>
	<datestamp>1268253960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Is measuring how one particular person performs over a limited amount of cellphone keyboards. Could be measuring here more things than just those keyboards. Take it as what it really mean.</htmltext>
<tokenext>Is measuring how one particular person performs over a limited amount of cellphone keyboards .
Could be measuring here more things than just those keyboards .
Take it as what it really mean .</tokentext>
<sentencetext>Is measuring how one particular person performs over a limited amount of cellphone keyboards.
Could be measuring here more things than just those keyboards.
Take it as what it really mean.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429876</id>
	<title>Swype</title>
	<author>LBArrettAnderson</author>
	<datestamp>1268253720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've been using Swype on my Nexus One for a month or two and it's incredible.  I wonder how it'd perform on that chart (Or is one of those phones the windows phone that includes it?  "Swype" didn't show up on the article page at all).</htmltext>
<tokenext>I 've been using Swype on my Nexus One for a month or two and it 's incredible .
I wonder how it 'd perform on that chart ( Or is one of those phones the windows phone that includes it ?
" Swype " did n't show up on the article page at all ) .</tokentext>
<sentencetext>I've been using Swype on my Nexus One for a month or two and it's incredible.
I wonder how it'd perform on that chart (Or is one of those phones the windows phone that includes it?
"Swype" didn't show up on the article page at all).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430502</id>
	<title>Yes, Barely Scientific</title>
	<author>Stenchwarrior</author>
	<datestamp>1268213400000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I think this is a completely legitimate question, but I agree with the author...it's barely scientific. Let's do this again with about 50 people, all who have little to no PDA experience and therefore no bias to one type or another. Then another 50 who are used to physical, and yet another 50 used to on-screen. Run the test and see what the results are. I'm sure more scientific<nobr> <wbr></nobr>/.ers out there have even better methods but this would at least offer more accurate results than what the author did.</htmltext>
<tokenext>I think this is a completely legitimate question , but I agree with the author...it 's barely scientific .
Let 's do this again with about 50 people , all who have little to no PDA experience and therefore no bias to one type or another .
Then another 50 who are used to physical , and yet another 50 used to on-screen .
Run the test and see what the results are .
I 'm sure more scientific /.ers out there have even better methods but this would at least offer more accurate results than what the author did .</tokentext>
<sentencetext>I think this is a completely legitimate question, but I agree with the author...it's barely scientific.
Let's do this again with about 50 people, all who have little to no PDA experience and therefore no bias to one type or another.
Then another 50 who are used to physical, and yet another 50 used to on-screen.
Run the test and see what the results are.
I'm sure more scientific /.ers out there have even better methods but this would at least offer more accurate results than what the author did.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31465250</id>
	<title>Re:Swype.</title>
	<author>srussell</author>
	<datestamp>1268507880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Ditto.  Actually, I was using ShapeWriter until Swype came out... they both have their nice points, but both of them are nice, and a lot of the time, I actually prefer them to hard keyboards.
<br> <br>
ShapeWriter has a really clever capitalization mechanism that I miss in Swype.  Often.  Swype has slightly better matching.  ShapeWriter will insert a space between a period and the next word; Swype doesn't (grrr!).  ShapeWriter has an annoying feature where, if the text entry ends with punctuation, the editing of misspelled words doesn't work.  Swype requires you to actually swipe over apostrophes to get them (it doesn't recognize "its" as potentially being "it's").  They both have "alternate" keyboards, but ShapeWriter's alternate is much more useful (bigger keys, focused on numeric entry) -- although, both make getting to some common keys (:,<nobr> <wbr></nobr>/) uncommonly difficult.  For some reason, I find Swype much easier to use if I'm tap-typing -- and ShapeWriter is almost <em>impossible</em> to use for password entry (if you're like me and use mixed-case passwords), whereas Swype is useful.
<br> <br>
They're both good. I don't know about Swype, but I get regular updates from ShapeWriter.  I've been using Swype for the past couple of weeks; I think it annoys me less, but they're pretty darned close.</htmltext>
<tokenext>Ditto .
Actually , I was using ShapeWriter until Swype came out... they both have their nice points , but both of them are nice , and a lot of the time , I actually prefer them to hard keyboards .
ShapeWriter has a really clever capitalization mechanism that I miss in Swype .
Often. Swype has slightly better matching .
ShapeWriter will insert a space between a period and the next word ; Swype does n't ( grrr ! ) .
ShapeWriter has an annoying feature where , if the text entry ends with punctuation , the editing of misspelled words does n't work .
Swype requires you to actually swipe over apostrophes to get them ( it does n't recognize " its " as potentially being " it 's " ) .
They both have " alternate " keyboards , but ShapeWriter 's alternate is much more useful ( bigger keys , focused on numeric entry ) -- although , both make getting to some common keys ( : , / ) uncommonly difficult .
For some reason , I find Swype much easier to use if I 'm tap-typing -- and ShapeWriter is almost impossible to use for password entry ( if you 're like me and use mixed-case passwords ) , whereas Swype is useful .
They 're both good .
I do n't know about Swype , but I get regular updates from ShapeWriter .
I 've been using Swype for the past couple of weeks ; I think it annoys me less , but they 're pretty darned close .</tokentext>
<sentencetext>Ditto.
Actually, I was using ShapeWriter until Swype came out... they both have their nice points, but both of them are nice, and a lot of the time, I actually prefer them to hard keyboards.
ShapeWriter has a really clever capitalization mechanism that I miss in Swype.
Often.  Swype has slightly better matching.
ShapeWriter will insert a space between a period and the next word; Swype doesn't (grrr!).
ShapeWriter has an annoying feature where, if the text entry ends with punctuation, the editing of misspelled words doesn't work.
Swype requires you to actually swipe over apostrophes to get them (it doesn't recognize "its" as potentially being "it's").
They both have "alternate" keyboards, but ShapeWriter's alternate is much more useful (bigger keys, focused on numeric entry) -- although, both make getting to some common keys (:, /) uncommonly difficult.
For some reason, I find Swype much easier to use if I'm tap-typing -- and ShapeWriter is almost impossible to use for password entry (if you're like me and use mixed-case passwords), whereas Swype is useful.
They're both good.
I don't know about Swype, but I get regular updates from ShapeWriter.
I've been using Swype for the past couple of weeks; I think it annoys me less, but they're pretty darned close.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431288</id>
	<title>Get an external keyboard if you hate the phone one</title>
	<author>nikomo</author>
	<datestamp>1268217240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I have a Nokia E51 so it has the good old basic 3-letters and a number per key (except 7 has 4 letters). Today I ordered a 18&euro; bluetooth keyboard for my cellphone so I can type like mad on the cellphone.
Symbian-version of Putty + server at home + small, pocket-sized bluetooth keyboard + 3.5G connection = enjoyment</htmltext>
<tokenext>I have a Nokia E51 so it has the good old basic 3-letters and a number per key ( except 7 has 4 letters ) .
Today I ordered a 18    bluetooth keyboard for my cellphone so I can type like mad on the cellphone .
Symbian-version of Putty + server at home + small , pocket-sized bluetooth keyboard + 3.5G connection = enjoyment</tokentext>
<sentencetext>I have a Nokia E51 so it has the good old basic 3-letters and a number per key (except 7 has 4 letters).
Today I ordered a 18€ bluetooth keyboard for my cellphone so I can type like mad on the cellphone.
Symbian-version of Putty + server at home + small, pocket-sized bluetooth keyboard + 3.5G connection = enjoyment</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429864</id>
	<title>Re:Debate</title>
	<author>Anonymous</author>
	<datestamp>1268253720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>I prefer not to have a keyboard on my smartphone because typing on a tiny keyboard, whether physical or not, is an enormous pain in the ass and I try to avoid it whenever possible.  Since a tiny physical keyboard is only marginally less painful to use than the on-screen one, I'd prefer not to waste space with one.</htmltext>
<tokenext>I prefer not to have a keyboard on my smartphone because typing on a tiny keyboard , whether physical or not , is an enormous pain in the ass and I try to avoid it whenever possible .
Since a tiny physical keyboard is only marginally less painful to use than the on-screen one , I 'd prefer not to waste space with one .</tokentext>
<sentencetext>I prefer not to have a keyboard on my smartphone because typing on a tiny keyboard, whether physical or not, is an enormous pain in the ass and I try to avoid it whenever possible.
Since a tiny physical keyboard is only marginally less painful to use than the on-screen one, I'd prefer not to waste space with one.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31436262</id>
	<title>How did this make it?</title>
	<author>mix77</author>
	<datestamp>1268312160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How in the world did this make it? Are there no hardware stories at all?</htmltext>
<tokenext>How in the world did this make it ?
Are there no hardware stories at all ?</tokentext>
<sentencetext>How in the world did this make it?
Are there no hardware stories at all?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429962</id>
	<title>Re:Debate</title>
	<author>obarthelemy</author>
	<datestamp>1268254020000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'd rather have a choice: not carry a keyboard when I don't need one for maximum portability, and take along a small, or medium, or large, bluetooth keyboard, when I think I will.</p></htmltext>
<tokenext>I 'd rather have a choice : not carry a keyboard when I do n't need one for maximum portability , and take along a small , or medium , or large , bluetooth keyboard , when I think I will .</tokentext>
<sentencetext>I'd rather have a choice: not carry a keyboard when I don't need one for maximum portability, and take along a small, or medium, or large, bluetooth keyboard, when I think I will.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431604</id>
	<title>Missing Rinnger: the HTC hero!</title>
	<author>virtualXTC</author>
	<datestamp>1268218560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Disclaimer: I own a G1, nonetheless I'm fairly certain my view here is correct:<br>
<br>
The hero's with it's well spaced out keys would of crushed the others, and is the reason I didn't choose a clque, or mytouch/hero and why I haven't upgraded to the N900, droid or nexus one.  Moreover, I previously had a tilt (htc kaiser), and had tried the N900 for a couple weeks, the keyboards for both are very similar to the nokia 75.  Without the spacing between the keys, there's no way one can be as accurate as the hero (g1).</htmltext>
<tokenext>Disclaimer : I own a G1 , nonetheless I 'm fairly certain my view here is correct : The hero 's with it 's well spaced out keys would of crushed the others , and is the reason I did n't choose a clque , or mytouch/hero and why I have n't upgraded to the N900 , droid or nexus one .
Moreover , I previously had a tilt ( htc kaiser ) , and had tried the N900 for a couple weeks , the keyboards for both are very similar to the nokia 75 .
Without the spacing between the keys , there 's no way one can be as accurate as the hero ( g1 ) .</tokentext>
<sentencetext>Disclaimer: I own a G1, nonetheless I'm fairly certain my view here is correct:

The hero's with it's well spaced out keys would of crushed the others, and is the reason I didn't choose a clque, or mytouch/hero and why I haven't upgraded to the N900, droid or nexus one.
Moreover, I previously had a tilt (htc kaiser), and had tried the N900 for a couple weeks, the keyboards for both are very similar to the nokia 75.
Without the spacing between the keys, there's no way one can be as accurate as the hero (g1).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430458</id>
	<title>Why the iPhone keyboard is better</title>
	<author>kroyd</author>
	<datestamp>1268213160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The iPhone keyboard allows chording - that is, you can hold one key down, press another key, and the other key will be registered as a keypress as well. If you type with more than one finger (or thumb) this will improve the speed.<p>

This does not work on my Nexus One (android), but I'm not sure about the other platforms.</p><p>

Another alternative, which is probably faster than any of the tested keyboards is swype, where you just draw a line which represents the word. There is a public beta at <a href="http://beta.swype.com/" title="swype.com">http://beta.swype.com/</a> [swype.com] (Android only)</p></htmltext>
<tokenext>The iPhone keyboard allows chording - that is , you can hold one key down , press another key , and the other key will be registered as a keypress as well .
If you type with more than one finger ( or thumb ) this will improve the speed .
This does not work on my Nexus One ( android ) , but I 'm not sure about the other platforms .
Another alternative , which is probably faster than any of the tested keyboards is swype , where you just draw a line which represents the word .
There is a public beta at http : //beta.swype.com/ [ swype.com ] ( Android only )</tokentext>
<sentencetext>The iPhone keyboard allows chording - that is, you can hold one key down, press another key, and the other key will be registered as a keypress as well.
If you type with more than one finger (or thumb) this will improve the speed.
This does not work on my Nexus One (android), but I'm not sure about the other platforms.
Another alternative, which is probably faster than any of the tested keyboards is swype, where you just draw a line which represents the word.
There is a public beta at http://beta.swype.com/ [swype.com] (Android only)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874</id>
	<title>Bias?</title>
	<author>mewsenews</author>
	<datestamp>1268253720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>The author acknowledges that this test is barely scientific, but I'm left wondering why he didn't disclose which phone he actually uses day-to-day. The muscle memory he's built up using his primary smartphone should give a huge bias to the results.</p></htmltext>
<tokenext>The author acknowledges that this test is barely scientific , but I 'm left wondering why he did n't disclose which phone he actually uses day-to-day .
The muscle memory he 's built up using his primary smartphone should give a huge bias to the results .</tokentext>
<sentencetext>The author acknowledges that this test is barely scientific, but I'm left wondering why he didn't disclose which phone he actually uses day-to-day.
The muscle memory he's built up using his primary smartphone should give a huge bias to the results.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432516</id>
	<title>Missing option: handwriting!</title>
	<author>KlaymenDK</author>
	<datestamp>1268223600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have an Android phone, and while the on-screen keyboard is okay, it does have severe disadvantages (as explained by others above).</p><p>The thing that I miss the most is definitely handwriting recognition -- it allows a small device to have a relatively big UI during input, it is not affected by regional layout differences, and it's fairly easy to extend and personalise by the individual user. TealScript is a prime example, really, doing full-screen transparent handwriting capture for any application.</p><p>Too bad most (all?) modern phone OS'es are too badly broken to even allow something like this to be implemented by a 3rd party (or even without serious core OS design changes).</p></htmltext>
<tokenext>I have an Android phone , and while the on-screen keyboard is okay , it does have severe disadvantages ( as explained by others above ) .The thing that I miss the most is definitely handwriting recognition -- it allows a small device to have a relatively big UI during input , it is not affected by regional layout differences , and it 's fairly easy to extend and personalise by the individual user .
TealScript is a prime example , really , doing full-screen transparent handwriting capture for any application.Too bad most ( all ?
) modern phone OS'es are too badly broken to even allow something like this to be implemented by a 3rd party ( or even without serious core OS design changes ) .</tokentext>
<sentencetext>I have an Android phone, and while the on-screen keyboard is okay, it does have severe disadvantages (as explained by others above).The thing that I miss the most is definitely handwriting recognition -- it allows a small device to have a relatively big UI during input, it is not affected by regional layout differences, and it's fairly easy to extend and personalise by the individual user.
TealScript is a prime example, really, doing full-screen transparent handwriting capture for any application.Too bad most (all?
) modern phone OS'es are too badly broken to even allow something like this to be implemented by a 3rd party (or even without serious core OS design changes).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430424</id>
	<title>Only half the story</title>
	<author>nightfire-unique</author>
	<datestamp>1268213100000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Well, it was interesting to see the times he posted, but of course everyone here knows that learning a keyboard takes practice.  Months of practice.</p><p>By the end of it, I could type 100wpm on my Zaurus C760 - almost as fast as with a real keyboard.  I could type about 60 on my treo 650.  I've got an n900 now, and I've been hanging around 50.  So there <i>are</i> substantial variances in keyboard quality and layout (at least on these devices)<nobr> <wbr></nobr>.. but what was more interesting were the learning curves.  My speed doubled on the Treo in the first week.  It over doubled on the C760 (slowly, over its 5 year lifespan).  But I'm not getting any faster on the n900, sadly.</p><p>All of this aside.. the main problem with on-screen keyboards?</p><p> <b>They take up half (or more) of your display!</b> </p><p>This is one point I'm amazed people are able to get beyond.  Sure - it's a rare use case... but terminals are <b>unusable</b> with an on-screen keyboard.  More commonly, web forms are confusing.  I can't even imagine trying to work on a document or spreadsheet.  The screen constantly changes as you need to enter data!</p><p>I believe that if you can get by under those conditions, the speed difference between hardware and virtual keyboards is mostly irrelevant.  How much data entry are you really doing?</p></htmltext>
<tokenext>Well , it was interesting to see the times he posted , but of course everyone here knows that learning a keyboard takes practice .
Months of practice.By the end of it , I could type 100wpm on my Zaurus C760 - almost as fast as with a real keyboard .
I could type about 60 on my treo 650 .
I 've got an n900 now , and I 've been hanging around 50 .
So there are substantial variances in keyboard quality and layout ( at least on these devices ) .. but what was more interesting were the learning curves .
My speed doubled on the Treo in the first week .
It over doubled on the C760 ( slowly , over its 5 year lifespan ) .
But I 'm not getting any faster on the n900 , sadly.All of this aside.. the main problem with on-screen keyboards ?
They take up half ( or more ) of your display !
This is one point I 'm amazed people are able to get beyond .
Sure - it 's a rare use case... but terminals are unusable with an on-screen keyboard .
More commonly , web forms are confusing .
I ca n't even imagine trying to work on a document or spreadsheet .
The screen constantly changes as you need to enter data ! I believe that if you can get by under those conditions , the speed difference between hardware and virtual keyboards is mostly irrelevant .
How much data entry are you really doing ?</tokentext>
<sentencetext>Well, it was interesting to see the times he posted, but of course everyone here knows that learning a keyboard takes practice.
Months of practice.By the end of it, I could type 100wpm on my Zaurus C760 - almost as fast as with a real keyboard.
I could type about 60 on my treo 650.
I've got an n900 now, and I've been hanging around 50.
So there are substantial variances in keyboard quality and layout (at least on these devices) .. but what was more interesting were the learning curves.
My speed doubled on the Treo in the first week.
It over doubled on the C760 (slowly, over its 5 year lifespan).
But I'm not getting any faster on the n900, sadly.All of this aside.. the main problem with on-screen keyboards?
They take up half (or more) of your display!
This is one point I'm amazed people are able to get beyond.
Sure - it's a rare use case... but terminals are unusable with an on-screen keyboard.
More commonly, web forms are confusing.
I can't even imagine trying to work on a document or spreadsheet.
The screen constantly changes as you need to enter data!I believe that if you can get by under those conditions, the speed difference between hardware and virtual keyboards is mostly irrelevant.
How much data entry are you really doing?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430204</id>
	<title>iUsed</title>
	<author>natehoy</author>
	<datestamp>1268211960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>From TFA:</p><p><div class="quote"><p>I used each phone in its default mode, as it would present to a brand-new user out of the box. I counted one error for each wrong word in the main text and for each wrong character in the phone number, web address, username and password. In every test I tried not to look at the screen and typed as quickly as I could, allowing the phone to correct any errors. I&rsquo;m not the world&rsquo;s fastest typist, so I&rsquo;m sure some of you could easily beat the absolute times, but as a comparison between devices it&rsquo;s reasonably valid.</p></div><p>There's a LOT of use of the word "I" in there.  Could it be that he went through an exhaustive process to determine which phone met *gasp* his own personal preferences?</p><p>Well, Paul, that's fantastic.  In fact, I happen to agree with you.  But you haven't settled the "debate" for anyone but yourself.  I think most (but NOT ALL) people would likely agree that a hard keyboard is really tough to beat when you want to type in a lot of text.  I know typing anything into my wife's iPod Touch is, for my massively meaty paws, an exercise in utter frustration.  I think entering anything more than a URL in it should be given a "circle of hell" difficulty level.  And I've really honestly tried to make it work.  For those apps that support rotation, the wide-format keyboard is just barely adequate, but WHY DOESN'T SAFARI SUPPORT THIS!?!?!?</p><p>(breathes)  But I digress.</p><p>I've seen people who can absolutely whiz-bang on soft keyboards.  I don't understand it, but they can.  I've also seen people who (believe it or not) do not need to enter any major Tolstoy works into their mobile phone browser on a routine basis.  For those people, a hard keyboard is an utter waste of what could be useful screen.</p><p>Personally, you can have my Blackberry 8310 smartphone when you pry it from my cold, dead thumbs.  Or replace it with a newer Blackberry Curve (oooh!  shiny!  3G please!) or something else with a hard keyboard in a similar form factor.  I don't like the postage stamp of a screen, but I enter text.  A lot.  And I need a physical keyboard until voice recognition stops getting me visits from HR when "I like your idea" gets transcribed as "I'll lick you my dear".  I also want something durable, and slideouts seem rather breakable in my big meaty paws.</p><p>So the wide-candybar format with a postage stamp screen is a reasonable compromise.  I've been carrying it for about a year and a half now, and while there's always the "wow, if I could get a bigger screen I could have seen that", there's constantly the "oh, dear, I gotta type a whole paragraph, thank FSM for this real keyboard - wonder twin thumbs, ACTIVATE!"  I can type about 1/4 to 1/2 as fast as I can on a desktop keyboard, special characters are just one extra keypress unless they are truly bizarro ones, and it just gets done what I need to get done quickly.</p><p>J. L. Slimfingers might be able to throw an iPhone in the air and type "Moby Dick" on it while in flight before it lands.  For him, a large screen format is an excellent choice.</p><p>D. Elly Catflower might keep it in a shockproof case and only bring it out with great ceremony and lay it on a safety pad of fine Corinthian leather before using it.  For her, a slideout is ideal.  Lots of screen, full-on keyboard, and they'll treat it right.</p><p>Me?  Big meaty paws, a tendency to bash it against stuff, and a need to enter a lot of text.  I got the Blackberry 8310, put it in a big rubbery slipcover, and put that inside an 8800-style leather case.  It's at a year and a half, I don't dread typing on it, and it's still going strong with about 2 days of battery life between charges.  I haven't even managed to scratch the screen (though the stick-on screen protector helps).  I think I chose well.</p><p>For me.</p><p>Not for everyone else.</p></div>
	</htmltext>
<tokenext>From TFA : I used each phone in its default mode , as it would present to a brand-new user out of the box .
I counted one error for each wrong word in the main text and for each wrong character in the phone number , web address , username and password .
In every test I tried not to look at the screen and typed as quickly as I could , allowing the phone to correct any errors .
I    m not the world    s fastest typist , so I    m sure some of you could easily beat the absolute times , but as a comparison between devices it    s reasonably valid.There 's a LOT of use of the word " I " in there .
Could it be that he went through an exhaustive process to determine which phone met * gasp * his own personal preferences ? Well , Paul , that 's fantastic .
In fact , I happen to agree with you .
But you have n't settled the " debate " for anyone but yourself .
I think most ( but NOT ALL ) people would likely agree that a hard keyboard is really tough to beat when you want to type in a lot of text .
I know typing anything into my wife 's iPod Touch is , for my massively meaty paws , an exercise in utter frustration .
I think entering anything more than a URL in it should be given a " circle of hell " difficulty level .
And I 've really honestly tried to make it work .
For those apps that support rotation , the wide-format keyboard is just barely adequate , but WHY DOES N'T SAFARI SUPPORT THIS ! ? ! ? ! ?
( breathes ) But I digress.I 've seen people who can absolutely whiz-bang on soft keyboards .
I do n't understand it , but they can .
I 've also seen people who ( believe it or not ) do not need to enter any major Tolstoy works into their mobile phone browser on a routine basis .
For those people , a hard keyboard is an utter waste of what could be useful screen.Personally , you can have my Blackberry 8310 smartphone when you pry it from my cold , dead thumbs .
Or replace it with a newer Blackberry Curve ( oooh !
shiny ! 3G please !
) or something else with a hard keyboard in a similar form factor .
I do n't like the postage stamp of a screen , but I enter text .
A lot .
And I need a physical keyboard until voice recognition stops getting me visits from HR when " I like your idea " gets transcribed as " I 'll lick you my dear " .
I also want something durable , and slideouts seem rather breakable in my big meaty paws.So the wide-candybar format with a postage stamp screen is a reasonable compromise .
I 've been carrying it for about a year and a half now , and while there 's always the " wow , if I could get a bigger screen I could have seen that " , there 's constantly the " oh , dear , I got ta type a whole paragraph , thank FSM for this real keyboard - wonder twin thumbs , ACTIVATE !
" I can type about 1/4 to 1/2 as fast as I can on a desktop keyboard , special characters are just one extra keypress unless they are truly bizarro ones , and it just gets done what I need to get done quickly.J .
L. Slimfingers might be able to throw an iPhone in the air and type " Moby Dick " on it while in flight before it lands .
For him , a large screen format is an excellent choice.D .
Elly Catflower might keep it in a shockproof case and only bring it out with great ceremony and lay it on a safety pad of fine Corinthian leather before using it .
For her , a slideout is ideal .
Lots of screen , full-on keyboard , and they 'll treat it right.Me ?
Big meaty paws , a tendency to bash it against stuff , and a need to enter a lot of text .
I got the Blackberry 8310 , put it in a big rubbery slipcover , and put that inside an 8800-style leather case .
It 's at a year and a half , I do n't dread typing on it , and it 's still going strong with about 2 days of battery life between charges .
I have n't even managed to scratch the screen ( though the stick-on screen protector helps ) .
I think I chose well.For me.Not for everyone else .</tokentext>
<sentencetext>From TFA:I used each phone in its default mode, as it would present to a brand-new user out of the box.
I counted one error for each wrong word in the main text and for each wrong character in the phone number, web address, username and password.
In every test I tried not to look at the screen and typed as quickly as I could, allowing the phone to correct any errors.
I’m not the world’s fastest typist, so I’m sure some of you could easily beat the absolute times, but as a comparison between devices it’s reasonably valid.There's a LOT of use of the word "I" in there.
Could it be that he went through an exhaustive process to determine which phone met *gasp* his own personal preferences?Well, Paul, that's fantastic.
In fact, I happen to agree with you.
But you haven't settled the "debate" for anyone but yourself.
I think most (but NOT ALL) people would likely agree that a hard keyboard is really tough to beat when you want to type in a lot of text.
I know typing anything into my wife's iPod Touch is, for my massively meaty paws, an exercise in utter frustration.
I think entering anything more than a URL in it should be given a "circle of hell" difficulty level.
And I've really honestly tried to make it work.
For those apps that support rotation, the wide-format keyboard is just barely adequate, but WHY DOESN'T SAFARI SUPPORT THIS!?!?!?
(breathes)  But I digress.I've seen people who can absolutely whiz-bang on soft keyboards.
I don't understand it, but they can.
I've also seen people who (believe it or not) do not need to enter any major Tolstoy works into their mobile phone browser on a routine basis.
For those people, a hard keyboard is an utter waste of what could be useful screen.Personally, you can have my Blackberry 8310 smartphone when you pry it from my cold, dead thumbs.
Or replace it with a newer Blackberry Curve (oooh!
shiny!  3G please!
) or something else with a hard keyboard in a similar form factor.
I don't like the postage stamp of a screen, but I enter text.
A lot.
And I need a physical keyboard until voice recognition stops getting me visits from HR when "I like your idea" gets transcribed as "I'll lick you my dear".
I also want something durable, and slideouts seem rather breakable in my big meaty paws.So the wide-candybar format with a postage stamp screen is a reasonable compromise.
I've been carrying it for about a year and a half now, and while there's always the "wow, if I could get a bigger screen I could have seen that", there's constantly the "oh, dear, I gotta type a whole paragraph, thank FSM for this real keyboard - wonder twin thumbs, ACTIVATE!
"  I can type about 1/4 to 1/2 as fast as I can on a desktop keyboard, special characters are just one extra keypress unless they are truly bizarro ones, and it just gets done what I need to get done quickly.J.
L. Slimfingers might be able to throw an iPhone in the air and type "Moby Dick" on it while in flight before it lands.
For him, a large screen format is an excellent choice.D.
Elly Catflower might keep it in a shockproof case and only bring it out with great ceremony and lay it on a safety pad of fine Corinthian leather before using it.
For her, a slideout is ideal.
Lots of screen, full-on keyboard, and they'll treat it right.Me?
Big meaty paws, a tendency to bash it against stuff, and a need to enter a lot of text.
I got the Blackberry 8310, put it in a big rubbery slipcover, and put that inside an 8800-style leather case.
It's at a year and a half, I don't dread typing on it, and it's still going strong with about 2 days of battery life between charges.
I haven't even managed to scratch the screen (though the stick-on screen protector helps).
I think I chose well.For me.Not for everyone else.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429916</id>
	<title>"barely scientific"? Not even that.</title>
	<author>fuzzyfuzzyfungus</author>
	<datestamp>1268253840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Keyboarding, even within the context of a high quality desktop keyboard, is not  a natural act. I requires nontrivial practice to achieve speed and accuracy with low mental overhead.<br> <br>

Smartphone keyboards are ghastly little things, whose virtues lie more or less exclusively in being small enough to fit on smartphones. Each different one requires substantial practice and much of that practice isn't transferable between systems.<br> <br>

Having one person try them all for a few minutes is line noise, it tells us nothing.</htmltext>
<tokenext>Keyboarding , even within the context of a high quality desktop keyboard , is not a natural act .
I requires nontrivial practice to achieve speed and accuracy with low mental overhead .
Smartphone keyboards are ghastly little things , whose virtues lie more or less exclusively in being small enough to fit on smartphones .
Each different one requires substantial practice and much of that practice is n't transferable between systems .
Having one person try them all for a few minutes is line noise , it tells us nothing .</tokentext>
<sentencetext>Keyboarding, even within the context of a high quality desktop keyboard, is not  a natural act.
I requires nontrivial practice to achieve speed and accuracy with low mental overhead.
Smartphone keyboards are ghastly little things, whose virtues lie more or less exclusively in being small enough to fit on smartphones.
Each different one requires substantial practice and much of that practice isn't transferable between systems.
Having one person try them all for a few minutes is line noise, it tells us nothing.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430520</id>
	<title>Re:Subjective somewhat?</title>
	<author>natehoy</author>
	<datestamp>1268213460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>These 'tests' really require a decent sample size of users and a decent sample size of devices with said screens.</p></div><p>No.  Sorry, but no.</p><p>These 'tests' really require that you as a consumer go into a phone store, narrow down the selection based on what features you need, then grab each and every surviving model in your own sweaty paws, and spend 10 minutes with each.  This will quickly narrow down the choices.  Take your two finalists and spend a quality half hour with each.  Thank the salesperson for his/her Jobesian patience, then buy the one that works best for you based on actually using it for a while.</p><p>If you don't plan on using your phone for heavy-duty text entry, grab whatever appeals to you and make sure you can get basic stuff done with it.  If you plan on using it heavily, get to know the keyboards and which one works for you.  Pack a lunch.  Bring some goodies to share with the sales rep.  They'll appreciate the gesture.</p><p>Finger length and thickness, dexterity, need for screen space, and several hundred other factors all go into what phone is best for each individual.  Having 1,000 jamokes all tell you that 65\% of them prefer the keyboard on "Brand X" will be almost meaningless to any individual phone user.</p></div>
	</htmltext>
<tokenext>These 'tests ' really require a decent sample size of users and a decent sample size of devices with said screens.No .
Sorry , but no.These 'tests ' really require that you as a consumer go into a phone store , narrow down the selection based on what features you need , then grab each and every surviving model in your own sweaty paws , and spend 10 minutes with each .
This will quickly narrow down the choices .
Take your two finalists and spend a quality half hour with each .
Thank the salesperson for his/her Jobesian patience , then buy the one that works best for you based on actually using it for a while.If you do n't plan on using your phone for heavy-duty text entry , grab whatever appeals to you and make sure you can get basic stuff done with it .
If you plan on using it heavily , get to know the keyboards and which one works for you .
Pack a lunch .
Bring some goodies to share with the sales rep. They 'll appreciate the gesture.Finger length and thickness , dexterity , need for screen space , and several hundred other factors all go into what phone is best for each individual .
Having 1,000 jamokes all tell you that 65 \ % of them prefer the keyboard on " Brand X " will be almost meaningless to any individual phone user .</tokentext>
<sentencetext>These 'tests' really require a decent sample size of users and a decent sample size of devices with said screens.No.
Sorry, but no.These 'tests' really require that you as a consumer go into a phone store, narrow down the selection based on what features you need, then grab each and every surviving model in your own sweaty paws, and spend 10 minutes with each.
This will quickly narrow down the choices.
Take your two finalists and spend a quality half hour with each.
Thank the salesperson for his/her Jobesian patience, then buy the one that works best for you based on actually using it for a while.If you don't plan on using your phone for heavy-duty text entry, grab whatever appeals to you and make sure you can get basic stuff done with it.
If you plan on using it heavily, get to know the keyboards and which one works for you.
Pack a lunch.
Bring some goodies to share with the sales rep.  They'll appreciate the gesture.Finger length and thickness, dexterity, need for screen space, and several hundred other factors all go into what phone is best for each individual.
Having 1,000 jamokes all tell you that 65\% of them prefer the keyboard on "Brand X" will be almost meaningless to any individual phone user.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430904</id>
	<title>don't mod me redundant, but</title>
	<author>archangel9</author>
	<datestamp>1268215440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>He also didn't mention what order he tested the phones in.  If he wanted to be fair (not even going to stretch it to "scientific") he would type different passages, numbers and URLs on each phone.  I'm sure by the last test he had the text almost memorized, so the latter phones probably ended up with shorter times and less mistakes.  Just guessing, but the Nokia E75 and the Bold2 were probably last to be tested.</htmltext>
<tokenext>He also did n't mention what order he tested the phones in .
If he wanted to be fair ( not even going to stretch it to " scientific " ) he would type different passages , numbers and URLs on each phone .
I 'm sure by the last test he had the text almost memorized , so the latter phones probably ended up with shorter times and less mistakes .
Just guessing , but the Nokia E75 and the Bold2 were probably last to be tested .</tokentext>
<sentencetext>He also didn't mention what order he tested the phones in.
If he wanted to be fair (not even going to stretch it to "scientific") he would type different passages, numbers and URLs on each phone.
I'm sure by the last test he had the text almost memorized, so the latter phones probably ended up with shorter times and less mistakes.
Just guessing, but the Nokia E75 and the Bold2 were probably last to be tested.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429950</id>
	<title>Re:Debate</title>
	<author>DIplomatic</author>
	<datestamp>1268253960000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext>I have a BlackBerry Storm and I swear by RIM's SureType. (That's the one with 2 letters on each soft key) <p>The predictive text learns as I use the device and I can type incredibly fast on it. Lengthy correspondence is not a problem.</p><p>It's just my preference, but now I would never use a physical keyboard. The keys are tiny and fixed, whereas on my BB they are large and can change to match whatever input I happen to need. (letters, caps, symbols, web signs)</p><p>Just my two cents.</p></htmltext>
<tokenext>I have a BlackBerry Storm and I swear by RIM 's SureType .
( That 's the one with 2 letters on each soft key ) The predictive text learns as I use the device and I can type incredibly fast on it .
Lengthy correspondence is not a problem.It 's just my preference , but now I would never use a physical keyboard .
The keys are tiny and fixed , whereas on my BB they are large and can change to match whatever input I happen to need .
( letters , caps , symbols , web signs ) Just my two cents .</tokentext>
<sentencetext>I have a BlackBerry Storm and I swear by RIM's SureType.
(That's the one with 2 letters on each soft key) The predictive text learns as I use the device and I can type incredibly fast on it.
Lengthy correspondence is not a problem.It's just my preference, but now I would never use a physical keyboard.
The keys are tiny and fixed, whereas on my BB they are large and can change to match whatever input I happen to need.
(letters, caps, symbols, web signs)Just my two cents.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430568</id>
	<title>Re:Bias?</title>
	<author>Dan East</author>
	<datestamp>1268213700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Certainly.  Tests of this nature are completely, totally worthless.  His previous experience with other devices may actually be to the detriment of his performance with devices with dissimilar keyboard layouts.</p><p>A proper study would use a number of individuals.  Each would be given a phone, tested on that phone, instructed to use that phone over the course of a week, and then tested again.  Then they would move on to another phone.  Each individual would be given the phones in a different order, so the performance improvement gained through general use of smart phones, as well as growing familiarity with the testing process, wouldn't skew the results.</p></htmltext>
<tokenext>Certainly .
Tests of this nature are completely , totally worthless .
His previous experience with other devices may actually be to the detriment of his performance with devices with dissimilar keyboard layouts.A proper study would use a number of individuals .
Each would be given a phone , tested on that phone , instructed to use that phone over the course of a week , and then tested again .
Then they would move on to another phone .
Each individual would be given the phones in a different order , so the performance improvement gained through general use of smart phones , as well as growing familiarity with the testing process , would n't skew the results .</tokentext>
<sentencetext>Certainly.
Tests of this nature are completely, totally worthless.
His previous experience with other devices may actually be to the detriment of his performance with devices with dissimilar keyboard layouts.A proper study would use a number of individuals.
Each would be given a phone, tested on that phone, instructed to use that phone over the course of a week, and then tested again.
Then they would move on to another phone.
Each individual would be given the phones in a different order, so the performance improvement gained through general use of smart phones, as well as growing familiarity with the testing process, wouldn't skew the results.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31433444</id>
	<title>Re:Swype.</title>
	<author>Anonymous</author>
	<datestamp>1268230860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Too bad the Swype for Android beta is now closed.</p><p>But, I'm using it on Droid. I like it better than the physical keyboard most of the time. If I ever learn where the cursor keys are I will like it better still.</p></htmltext>
<tokenext>Too bad the Swype for Android beta is now closed.But , I 'm using it on Droid .
I like it better than the physical keyboard most of the time .
If I ever learn where the cursor keys are I will like it better still .</tokentext>
<sentencetext>Too bad the Swype for Android beta is now closed.But, I'm using it on Droid.
I like it better than the physical keyboard most of the time.
If I ever learn where the cursor keys are I will like it better still.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432044</id>
	<title>Re:Debate</title>
	<author>Internal Modem</author>
	<datestamp>1268220720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yes. I prefer a screen that has a dual use considering the limited real estate.

The concept allows sharing a multi funtion over time rather than space...</htmltext>
<tokenext>Yes .
I prefer a screen that has a dual use considering the limited real estate .
The concept allows sharing a multi funtion over time rather than space.. .</tokentext>
<sentencetext>Yes.
I prefer a screen that has a dual use considering the limited real estate.
The concept allows sharing a multi funtion over time rather than space...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430676</id>
	<title>Virtual Keyboard - glass or plastic screen?</title>
	<author>Hodar</author>
	<datestamp>1268214240000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>All virtual keyboards are NOT created equal.</p><p>One of the primary differences is the backing material of the touch screen.  The cheaper phones utilize a plastic backing on the touchscreen, this plastic will bend, warp and cause 'typos' even if your finge is precisely where it's supposed to be.  Glass does not flex, or warp - but is more expensive.  This is why the iPhone gives such a superior performance on the virtual keyboard, as they have a glass backing.</p><p>I think many of the problems with virtual keyboards is due to the cheaper touchscreens utilize the flexible plastic backing behind the flexible membrane - thus adding distortion to the pressure point matrix - resulting in typo's that are indeed the "phone's fault".</p><p>It would be interesting to see this sort of study conducted with external keyboards, virtual (glass) and virtual (plastic) keyboards.</p><p>I'm switching to the Droid for the option of not only abandoning my cheap plastic backing on my touchscreen LG Dare; but also because I'll have the option of the slide out keyboard.</p></htmltext>
<tokenext>All virtual keyboards are NOT created equal.One of the primary differences is the backing material of the touch screen .
The cheaper phones utilize a plastic backing on the touchscreen , this plastic will bend , warp and cause 'typos ' even if your finge is precisely where it 's supposed to be .
Glass does not flex , or warp - but is more expensive .
This is why the iPhone gives such a superior performance on the virtual keyboard , as they have a glass backing.I think many of the problems with virtual keyboards is due to the cheaper touchscreens utilize the flexible plastic backing behind the flexible membrane - thus adding distortion to the pressure point matrix - resulting in typo 's that are indeed the " phone 's fault " .It would be interesting to see this sort of study conducted with external keyboards , virtual ( glass ) and virtual ( plastic ) keyboards.I 'm switching to the Droid for the option of not only abandoning my cheap plastic backing on my touchscreen LG Dare ; but also because I 'll have the option of the slide out keyboard .</tokentext>
<sentencetext>All virtual keyboards are NOT created equal.One of the primary differences is the backing material of the touch screen.
The cheaper phones utilize a plastic backing on the touchscreen, this plastic will bend, warp and cause 'typos' even if your finge is precisely where it's supposed to be.
Glass does not flex, or warp - but is more expensive.
This is why the iPhone gives such a superior performance on the virtual keyboard, as they have a glass backing.I think many of the problems with virtual keyboards is due to the cheaper touchscreens utilize the flexible plastic backing behind the flexible membrane - thus adding distortion to the pressure point matrix - resulting in typo's that are indeed the "phone's fault".It would be interesting to see this sort of study conducted with external keyboards, virtual (glass) and virtual (plastic) keyboards.I'm switching to the Droid for the option of not only abandoning my cheap plastic backing on my touchscreen LG Dare; but also because I'll have the option of the slide out keyboard.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31436256</id>
	<title>No Nokia 900?</title>
	<author>RichiH</author>
	<datestamp>1268312100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Everyone who has ever tried both the E75 and the N900 knows that the N900 beats the E75 hands down. I don't know how they could not include that in the test. Pity, really.</p></htmltext>
<tokenext>Everyone who has ever tried both the E75 and the N900 knows that the N900 beats the E75 hands down .
I do n't know how they could not include that in the test .
Pity , really .</tokentext>
<sentencetext>Everyone who has ever tried both the E75 and the N900 knows that the N900 beats the E75 hands down.
I don't know how they could not include that in the test.
Pity, really.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430188</id>
	<title>Virtual keyboards?  Why not Dasher?</title>
	<author>Anonymous</author>
	<datestamp>1268211900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Since touch typing on virtual keyboards is impossible and hence one must be looking at the screen at all times, why not just replace them with a more efficient method such as <a href="http://www.inference.phy.cam.ac.uk/dasher/" title="cam.ac.uk" rel="nofollow">Dasher</a> [cam.ac.uk]?  The only downsides I can think of is need for a language-specific predictive model (though it could learn from the user and still be more effective than a virtual keyboard) and lack of support for chording, which could make text entry even more efficient.</p></htmltext>
<tokenext>Since touch typing on virtual keyboards is impossible and hence one must be looking at the screen at all times , why not just replace them with a more efficient method such as Dasher [ cam.ac.uk ] ?
The only downsides I can think of is need for a language-specific predictive model ( though it could learn from the user and still be more effective than a virtual keyboard ) and lack of support for chording , which could make text entry even more efficient .</tokentext>
<sentencetext>Since touch typing on virtual keyboards is impossible and hence one must be looking at the screen at all times, why not just replace them with a more efficient method such as Dasher [cam.ac.uk]?
The only downsides I can think of is need for a language-specific predictive model (though it could learn from the user and still be more effective than a virtual keyboard) and lack of support for chording, which could make text entry even more efficient.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431070</id>
	<title>Re:"barely scientific"? Not even that.</title>
	<author>ectoraige</author>
	<datestamp>1268216100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It tells us how quickly one person adapts to a sample new input systems. It's a data point, and he even described the methodology allowing others to repeat, so yeah, I think it counts as barely scientific.</p></htmltext>
<tokenext>It tells us how quickly one person adapts to a sample new input systems .
It 's a data point , and he even described the methodology allowing others to repeat , so yeah , I think it counts as barely scientific .</tokentext>
<sentencetext>It tells us how quickly one person adapts to a sample new input systems.
It's a data point, and he even described the methodology allowing others to repeat, so yeah, I think it counts as barely scientific.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429916</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430348</id>
	<title>My $.02...</title>
	<author>sootman</author>
	<datestamp>1268212800000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I've owned two Nokias with physical keyboards (6800 and 6820) and a BlackBerry (Curve 8330--not the best) and an iPhone, and I prefer the iPhone's virtual keyboard by far. Not so much for speed, though some basic testing by me shows they're all comparable, but for <em>ease.</em> The <a href="http://engage.htmhell.com/images/uploads/nokia6800duo.jpg" title="htmhell.com">6800</a> [htmhell.com] is large with plastic between the nicely-rounded keys and it's very easy to hit the right one. The <a href="http://www.juliepenner.com/blog/wp-content/uploads/2008/07/nokia\_6820\_phone.jpg" title="juliepenner.com">6820</a> [juliepenner.com] is a bit smaller but the keys are also nicely rounded and typing on that is pretty easy. Both also have dedicated buttons for numbers and some punctuation--hyphen, comma, period, slash, single quote, and more are all primary buttons. Their layouts also closely mimic a PC keyboard with comma, period, slash, semicolon, quote, and equals in roughly the same spots as on a regular keyboard.</p><p>The BlackBerry's keys are smaller and closer together and firmer than either Nokia and I find I've got to press on them with a thumbnail or the bony part of a finger to get them to register and not mash more than one key at a time, and <a href="http://susansternberg.files.wordpress.com/2009/07/blackberry-curve-8330-sprint1.jpg" title="wordpress.com">there are no number or punctuation keys AT ALL</a> [wordpress.com] which makes typing just about anything quite a pain.</p><p>The iPhone only shows letters or numbers/punctuation but since it's virtual the secondary and tertiary buttons are big and easy to find, not like the tiny glyphs you get from sticking two images on one physical key. But the thing I like most about virtual keys is that it only takes a very light tough to register a press, and the clickable area is very large, so typing with the biggest, roundest, softest part of your thumb is a cinch. And because of this, it is by far the easiest to use with one hand. (Though the split-keyboard Nokias are pretty much out of the running in this area, but the BB is similar in size and shape.)</p><p>But anyway, that's just my experience and preference. All that matters is what works best <em>for you.</em></p></div>
	</htmltext>
<tokenext>I 've owned two Nokias with physical keyboards ( 6800 and 6820 ) and a BlackBerry ( Curve 8330--not the best ) and an iPhone , and I prefer the iPhone 's virtual keyboard by far .
Not so much for speed , though some basic testing by me shows they 're all comparable , but for ease .
The 6800 [ htmhell.com ] is large with plastic between the nicely-rounded keys and it 's very easy to hit the right one .
The 6820 [ juliepenner.com ] is a bit smaller but the keys are also nicely rounded and typing on that is pretty easy .
Both also have dedicated buttons for numbers and some punctuation--hyphen , comma , period , slash , single quote , and more are all primary buttons .
Their layouts also closely mimic a PC keyboard with comma , period , slash , semicolon , quote , and equals in roughly the same spots as on a regular keyboard.The BlackBerry 's keys are smaller and closer together and firmer than either Nokia and I find I 've got to press on them with a thumbnail or the bony part of a finger to get them to register and not mash more than one key at a time , and there are no number or punctuation keys AT ALL [ wordpress.com ] which makes typing just about anything quite a pain.The iPhone only shows letters or numbers/punctuation but since it 's virtual the secondary and tertiary buttons are big and easy to find , not like the tiny glyphs you get from sticking two images on one physical key .
But the thing I like most about virtual keys is that it only takes a very light tough to register a press , and the clickable area is very large , so typing with the biggest , roundest , softest part of your thumb is a cinch .
And because of this , it is by far the easiest to use with one hand .
( Though the split-keyboard Nokias are pretty much out of the running in this area , but the BB is similar in size and shape .
) But anyway , that 's just my experience and preference .
All that matters is what works best for you .</tokentext>
<sentencetext>I've owned two Nokias with physical keyboards (6800 and 6820) and a BlackBerry (Curve 8330--not the best) and an iPhone, and I prefer the iPhone's virtual keyboard by far.
Not so much for speed, though some basic testing by me shows they're all comparable, but for ease.
The 6800 [htmhell.com] is large with plastic between the nicely-rounded keys and it's very easy to hit the right one.
The 6820 [juliepenner.com] is a bit smaller but the keys are also nicely rounded and typing on that is pretty easy.
Both also have dedicated buttons for numbers and some punctuation--hyphen, comma, period, slash, single quote, and more are all primary buttons.
Their layouts also closely mimic a PC keyboard with comma, period, slash, semicolon, quote, and equals in roughly the same spots as on a regular keyboard.The BlackBerry's keys are smaller and closer together and firmer than either Nokia and I find I've got to press on them with a thumbnail or the bony part of a finger to get them to register and not mash more than one key at a time, and there are no number or punctuation keys AT ALL [wordpress.com] which makes typing just about anything quite a pain.The iPhone only shows letters or numbers/punctuation but since it's virtual the secondary and tertiary buttons are big and easy to find, not like the tiny glyphs you get from sticking two images on one physical key.
But the thing I like most about virtual keys is that it only takes a very light tough to register a press, and the clickable area is very large, so typing with the biggest, roundest, softest part of your thumb is a cinch.
And because of this, it is by far the easiest to use with one hand.
(Though the split-keyboard Nokias are pretty much out of the running in this area, but the BB is similar in size and shape.
)But anyway, that's just my experience and preference.
All that matters is what works best for you.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31435778</id>
	<title>Re:Swype.</title>
	<author>strikethree</author>
	<datestamp>1268303520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have an iPhone, a Nokia N900, and a Nokia 5800. The 5800 touchscreen was just horrible, but it worked very well with the stylus. Unfortunately, the stylus is not a serious input device. My iPhone, turned sideways, allows me to use both thumbs and hold the device comfortably. After some weeks of practice, I can type almost entire dissertations on it quickly. The 'M' button and the spacebar seem to get mixed up at times as does the Shift and the 'A' key, but otherwise, the iPhone input rocks.</p><p>That being said, I fucking hate my iPhone. The only reason I use it at all is that I was able to jailbreak and unlock it and it has superior input capabilities... so, I went out and bought a Nokia N900. Now, this is a real phone. The only reason I still use my iPhone over my N900 is that the keyboard is not so good. I have tried a friends Nokia (N97?) and the keys were spaced just a bit further apart and with practice, could have become a useful input feature. The N900 has keys that are way too close and the 'click' sound feedback is hit and miss, so sometimes, I end up hitting the same key over and over again because I thought it did not take the first time.</p><p>All in all, the iPhone is the only onscreen keyboard that I have ever tried that is even useful at all... and it is VERY good. Some of the Nokia phones have semi-decent keyboards, but the N900 is NOT one of them. If you are buying a phone purely for its input capabilities, buy an iPhone and don't look back (because you will see Steve Jobs doing things to your anal opening!).</p><p>strike</p></htmltext>
<tokenext>I have an iPhone , a Nokia N900 , and a Nokia 5800 .
The 5800 touchscreen was just horrible , but it worked very well with the stylus .
Unfortunately , the stylus is not a serious input device .
My iPhone , turned sideways , allows me to use both thumbs and hold the device comfortably .
After some weeks of practice , I can type almost entire dissertations on it quickly .
The 'M ' button and the spacebar seem to get mixed up at times as does the Shift and the 'A ' key , but otherwise , the iPhone input rocks.That being said , I fucking hate my iPhone .
The only reason I use it at all is that I was able to jailbreak and unlock it and it has superior input capabilities... so , I went out and bought a Nokia N900 .
Now , this is a real phone .
The only reason I still use my iPhone over my N900 is that the keyboard is not so good .
I have tried a friends Nokia ( N97 ?
) and the keys were spaced just a bit further apart and with practice , could have become a useful input feature .
The N900 has keys that are way too close and the 'click ' sound feedback is hit and miss , so sometimes , I end up hitting the same key over and over again because I thought it did not take the first time.All in all , the iPhone is the only onscreen keyboard that I have ever tried that is even useful at all... and it is VERY good .
Some of the Nokia phones have semi-decent keyboards , but the N900 is NOT one of them .
If you are buying a phone purely for its input capabilities , buy an iPhone and do n't look back ( because you will see Steve Jobs doing things to your anal opening !
) .strike</tokentext>
<sentencetext>I have an iPhone, a Nokia N900, and a Nokia 5800.
The 5800 touchscreen was just horrible, but it worked very well with the stylus.
Unfortunately, the stylus is not a serious input device.
My iPhone, turned sideways, allows me to use both thumbs and hold the device comfortably.
After some weeks of practice, I can type almost entire dissertations on it quickly.
The 'M' button and the spacebar seem to get mixed up at times as does the Shift and the 'A' key, but otherwise, the iPhone input rocks.That being said, I fucking hate my iPhone.
The only reason I use it at all is that I was able to jailbreak and unlock it and it has superior input capabilities... so, I went out and bought a Nokia N900.
Now, this is a real phone.
The only reason I still use my iPhone over my N900 is that the keyboard is not so good.
I have tried a friends Nokia (N97?
) and the keys were spaced just a bit further apart and with practice, could have become a useful input feature.
The N900 has keys that are way too close and the 'click' sound feedback is hit and miss, so sometimes, I end up hitting the same key over and over again because I thought it did not take the first time.All in all, the iPhone is the only onscreen keyboard that I have ever tried that is even useful at all... and it is VERY good.
Some of the Nokia phones have semi-decent keyboards, but the N900 is NOT one of them.
If you are buying a phone purely for its input capabilities, buy an iPhone and don't look back (because you will see Steve Jobs doing things to your anal opening!
).strike</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848</id>
	<title>Swype.</title>
	<author>Karganeth</author>
	<datestamp>1268253660000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>I downloaded swype for my Nexus One and haven't looked back.  It's so much faster than the old virtual keyboard for "hunt and peck". The videos of it don't do it justice.  It's much easier and faster than the old ways.</htmltext>
<tokenext>I downloaded swype for my Nexus One and have n't looked back .
It 's so much faster than the old virtual keyboard for " hunt and peck " .
The videos of it do n't do it justice .
It 's much easier and faster than the old ways .</tokentext>
<sentencetext>I downloaded swype for my Nexus One and haven't looked back.
It's so much faster than the old virtual keyboard for "hunt and peck".
The videos of it don't do it justice.
It's much easier and faster than the old ways.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31434582</id>
	<title>Lame</title>
	<author>LandGator</author>
	<datestamp>1268242980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Test didn't include the Nokia E90, far and away the best keyboard of any smartphone (6 rows).</htmltext>
<tokenext>Test did n't include the Nokia E90 , far and away the best keyboard of any smartphone ( 6 rows ) .</tokentext>
<sentencetext>Test didn't include the Nokia E90, far and away the best keyboard of any smartphone (6 rows).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432174</id>
	<title>Meh</title>
	<author>binford2k</author>
	<datestamp>1268221380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>All this article shows is that the author can type better on a physical keyboard.  Nothing else.  What a waste of 30 seconds of my time.</p></htmltext>
<tokenext>All this article shows is that the author can type better on a physical keyboard .
Nothing else .
What a waste of 30 seconds of my time .</tokentext>
<sentencetext>All this article shows is that the author can type better on a physical keyboard.
Nothing else.
What a waste of 30 seconds of my time.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31439028</id>
	<title>Virtual keyboards are not for good typists</title>
	<author>isoutar</author>
	<datestamp>1268327760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If you are good at typing you can do it in the dark at high speed.   Impossible on a virtual keyboard with any accuracy.

I have abandoned all my devices that use virtual keyboards.   Netbooks for me<nobr> <wbr></nobr>... never a tablet!

Ian Soutar
Victoria BC
<a href="http://www.microsec.net/" title="microsec.net" rel="nofollow">http://www.microsec.net/</a> [microsec.net]</htmltext>
<tokenext>If you are good at typing you can do it in the dark at high speed .
Impossible on a virtual keyboard with any accuracy .
I have abandoned all my devices that use virtual keyboards .
Netbooks for me ... never a tablet !
Ian Soutar Victoria BC http : //www.microsec.net/ [ microsec.net ]</tokentext>
<sentencetext>If you are good at typing you can do it in the dark at high speed.
Impossible on a virtual keyboard with any accuracy.
I have abandoned all my devices that use virtual keyboards.
Netbooks for me ... never a tablet!
Ian Soutar
Victoria BC
http://www.microsec.net/ [microsec.net]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430532</id>
	<title>phone=a computer with skype installed</title>
	<author>BlackShirt</author>
	<datestamp>1268213520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Where I could by a decent phone with wifi connection and qwerty keyboard? I could buy some fancy phones (iphone, xperia, blackberry,nokia e72)  but no dirt cheap models. I tried ipod touch but it feels cold and too heavy on the hand.</p><p>Samsung GT-B3410 sounds most reasonable option. Lacks wifi.<br><a href="http://www.pda-247.com/wordpress/2009/12/a-smartphone-for-under-80-meet-the-samsung-gt-b3410/" title="pda-247.com" rel="nofollow">http://www.pda-247.com/wordpress/2009/12/a-smartphone-for-under-80-meet-the-samsung-gt-b3410/</a> [pda-247.com]</p></htmltext>
<tokenext>Where I could by a decent phone with wifi connection and qwerty keyboard ?
I could buy some fancy phones ( iphone , xperia , blackberry,nokia e72 ) but no dirt cheap models .
I tried ipod touch but it feels cold and too heavy on the hand.Samsung GT-B3410 sounds most reasonable option .
Lacks wifi.http : //www.pda-247.com/wordpress/2009/12/a-smartphone-for-under-80-meet-the-samsung-gt-b3410/ [ pda-247.com ]</tokentext>
<sentencetext>Where I could by a decent phone with wifi connection and qwerty keyboard?
I could buy some fancy phones (iphone, xperia, blackberry,nokia e72)  but no dirt cheap models.
I tried ipod touch but it feels cold and too heavy on the hand.Samsung GT-B3410 sounds most reasonable option.
Lacks wifi.http://www.pda-247.com/wordpress/2009/12/a-smartphone-for-under-80-meet-the-samsung-gt-b3410/ [pda-247.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31433918</id>
	<title>Re:Hardly a Significant Test</title>
	<author>Slack0ff</author>
	<datestamp>1268235600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I can't believe the author didn't feel the need to disclose his day to day phone. As a long time Blackberry owner I'm sure my results would be just as skewed towards the Bold 9700. However, I've seen an iPhone user on a Blackberry and can't say they quite got it first try.</htmltext>
<tokenext>I ca n't believe the author did n't feel the need to disclose his day to day phone .
As a long time Blackberry owner I 'm sure my results would be just as skewed towards the Bold 9700 .
However , I 've seen an iPhone user on a Blackberry and ca n't say they quite got it first try .</tokentext>
<sentencetext>I can't believe the author didn't feel the need to disclose his day to day phone.
As a long time Blackberry owner I'm sure my results would be just as skewed towards the Bold 9700.
However, I've seen an iPhone user on a Blackberry and can't say they quite got it first try.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430056</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430716</id>
	<title>Re:Bias?</title>
	<author>jtownatpunk.net</author>
	<datestamp>1268214480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Barely scientific"?  It's barely a "test".  I don't see my phone listed on there.  I can use a virtual keyboard with or without vibration feedback in portrait or landscape.  I can also slide the display to expose the 4-row, physical qwerty keyboard.  And, now that I think about it, I wonder if I can pair this bluetooth keyboard with it......</p></htmltext>
<tokenext>" Barely scientific " ?
It 's barely a " test " .
I do n't see my phone listed on there .
I can use a virtual keyboard with or without vibration feedback in portrait or landscape .
I can also slide the display to expose the 4-row , physical qwerty keyboard .
And , now that I think about it , I wonder if I can pair this bluetooth keyboard with it..... .</tokentext>
<sentencetext>"Barely scientific"?
It's barely a "test".
I don't see my phone listed on there.
I can use a virtual keyboard with or without vibration feedback in portrait or landscape.
I can also slide the display to expose the 4-row, physical qwerty keyboard.
And, now that I think about it, I wonder if I can pair this bluetooth keyboard with it......</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430056</id>
	<title>Hardly a Significant Test</title>
	<author>SlashdotOgre</author>
	<datestamp>1268254440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>I'm sorry, but one person typing a short message, is not going to tell us anything significant.  Furthermore we don't know his background (e.g. what types of phones/PDA's he's used in the past), or how "fat" his fingers are.  At best all we know is what phone he's best at right now.  The performance of the same person when they first used the phone compared to that same person after owning that type of phone for a year will differ significantly.</p><p>If someone plans to type on their phone enough for the difference of a few seconds to matter, then they really need to compare the phones in person themselves. A significantly larger sample of people ideally who have never used a phone with a full keyboard may give some idea of which styles tend to work better on average, but that's about the most information you'll get.  Whether it works best (and is comfortable) for you is something you need to try yourself.</p></htmltext>
<tokenext>I 'm sorry , but one person typing a short message , is not going to tell us anything significant .
Furthermore we do n't know his background ( e.g .
what types of phones/PDA 's he 's used in the past ) , or how " fat " his fingers are .
At best all we know is what phone he 's best at right now .
The performance of the same person when they first used the phone compared to that same person after owning that type of phone for a year will differ significantly.If someone plans to type on their phone enough for the difference of a few seconds to matter , then they really need to compare the phones in person themselves .
A significantly larger sample of people ideally who have never used a phone with a full keyboard may give some idea of which styles tend to work better on average , but that 's about the most information you 'll get .
Whether it works best ( and is comfortable ) for you is something you need to try yourself .</tokentext>
<sentencetext>I'm sorry, but one person typing a short message, is not going to tell us anything significant.
Furthermore we don't know his background (e.g.
what types of phones/PDA's he's used in the past), or how "fat" his fingers are.
At best all we know is what phone he's best at right now.
The performance of the same person when they first used the phone compared to that same person after owning that type of phone for a year will differ significantly.If someone plans to type on their phone enough for the difference of a few seconds to matter, then they really need to compare the phones in person themselves.
A significantly larger sample of people ideally who have never used a phone with a full keyboard may give some idea of which styles tend to work better on average, but that's about the most information you'll get.
Whether it works best (and is comfortable) for you is something you need to try yourself.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430468</id>
	<title>Re:Subjective somewhat?</title>
	<author>zullnero</author>
	<datestamp>1268213220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Exactly.  I have a vertical slider because I use my phone vertically about 90\% more than I use it horizontally, and having to spin my phone just to send a text message annoys me.  I also prefer a smaller keyboard because I know it shrinks the device profile and fits better in the pocket...I don't need a Blackberry keyboard, not at all.  So when I type messages out on my Pre with a vertical slide out keyboard, I'm about as fast as anyone else...but when I hand my phone off to a BB person, they start cursing because they're used to moving their thumbs a further distance to reach keys and they make more typos.  They have learned motions that they have to retrain themselves on.  Inversely, I have a tougher time typing on those side slider keyboards because I'm used to shorter reaches with the thumbs.</htmltext>
<tokenext>Exactly .
I have a vertical slider because I use my phone vertically about 90 \ % more than I use it horizontally , and having to spin my phone just to send a text message annoys me .
I also prefer a smaller keyboard because I know it shrinks the device profile and fits better in the pocket...I do n't need a Blackberry keyboard , not at all .
So when I type messages out on my Pre with a vertical slide out keyboard , I 'm about as fast as anyone else...but when I hand my phone off to a BB person , they start cursing because they 're used to moving their thumbs a further distance to reach keys and they make more typos .
They have learned motions that they have to retrain themselves on .
Inversely , I have a tougher time typing on those side slider keyboards because I 'm used to shorter reaches with the thumbs .</tokentext>
<sentencetext>Exactly.
I have a vertical slider because I use my phone vertically about 90\% more than I use it horizontally, and having to spin my phone just to send a text message annoys me.
I also prefer a smaller keyboard because I know it shrinks the device profile and fits better in the pocket...I don't need a Blackberry keyboard, not at all.
So when I type messages out on my Pre with a vertical slide out keyboard, I'm about as fast as anyone else...but when I hand my phone off to a BB person, they start cursing because they're used to moving their thumbs a further distance to reach keys and they make more typos.
They have learned motions that they have to retrain themselves on.
Inversely, I have a tougher time typing on those side slider keyboards because I'm used to shorter reaches with the thumbs.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430078</id>
	<title>Results are in a picture of a table...</title>
	<author>Anonymous</author>
	<datestamp>1268254560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>There's a pictutre of a table with the results. For anyone who is not able to read the information in the picture, here's what it says:</p><p>Fastest (1m44s), with 0 errors: BlackBerry Bold 2 with physical keyboard below screen.</p><p>Slowest (3m24s), with most (9) errors: BlackBerry Storm 2 that has an on-screen keyboard with "click feedback".</p><p>Second best, both in terms of errors (0) and speed (2m0s) was Nokia E 75 with a physical, slide out keyboard.</p><p>iPhone 3 GS with on-screen keyboard took 2m43s and got 2 errors.</p><p>Other participants: HTC Hero and HTC Touch HD2, that have on-screen keyboards with "vibrate feedback" (3m1s, 2m41s, respectively, with 4 and 1 error(s), respectively).</p></htmltext>
<tokenext>There 's a pictutre of a table with the results .
For anyone who is not able to read the information in the picture , here 's what it says : Fastest ( 1m44s ) , with 0 errors : BlackBerry Bold 2 with physical keyboard below screen.Slowest ( 3m24s ) , with most ( 9 ) errors : BlackBerry Storm 2 that has an on-screen keyboard with " click feedback " .Second best , both in terms of errors ( 0 ) and speed ( 2m0s ) was Nokia E 75 with a physical , slide out keyboard.iPhone 3 GS with on-screen keyboard took 2m43s and got 2 errors.Other participants : HTC Hero and HTC Touch HD2 , that have on-screen keyboards with " vibrate feedback " ( 3m1s , 2m41s , respectively , with 4 and 1 error ( s ) , respectively ) .</tokentext>
<sentencetext>There's a pictutre of a table with the results.
For anyone who is not able to read the information in the picture, here's what it says:Fastest (1m44s), with 0 errors: BlackBerry Bold 2 with physical keyboard below screen.Slowest (3m24s), with most (9) errors: BlackBerry Storm 2 that has an on-screen keyboard with "click feedback".Second best, both in terms of errors (0) and speed (2m0s) was Nokia E 75 with a physical, slide out keyboard.iPhone 3 GS with on-screen keyboard took 2m43s and got 2 errors.Other participants: HTC Hero and HTC Touch HD2, that have on-screen keyboards with "vibrate feedback" (3m1s, 2m41s, respectively, with 4 and 1 error(s), respectively).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430396</id>
	<title>Why physical keyboard is better</title>
	<author>Spy Handler</author>
	<datestamp>1268212980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>for <a href="http://www.thebestpageintheuniverse.net/c.cgi?u=iphone" title="thebestpag...iverse.net">typing text</a> [thebestpag...iverse.net]</htmltext>
<tokenext>for typing text [ thebestpag...iverse.net ]</tokentext>
<sentencetext>for typing text [thebestpag...iverse.net]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430274</id>
	<title>I have both kinds of keyboards</title>
	<author>generalhavok</author>
	<datestamp>1268212320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I have a Droid.  Therefore I don't have to decide if I want to use an on screen keyboard or a conventional keyboard.  I have both.  I have my cake and I get to eat it too.  Although I'm not sure which I prefer, as I use both the on-screen and regular keyboard about equally, I think I'm a little faster with the regular keyboard.  But for a short text, sometimes it's more convenient to just use the on-screen.  Otherwise, I didn't find this article too worth-while.</htmltext>
<tokenext>I have a Droid .
Therefore I do n't have to decide if I want to use an on screen keyboard or a conventional keyboard .
I have both .
I have my cake and I get to eat it too .
Although I 'm not sure which I prefer , as I use both the on-screen and regular keyboard about equally , I think I 'm a little faster with the regular keyboard .
But for a short text , sometimes it 's more convenient to just use the on-screen .
Otherwise , I did n't find this article too worth-while .</tokentext>
<sentencetext>I have a Droid.
Therefore I don't have to decide if I want to use an on screen keyboard or a conventional keyboard.
I have both.
I have my cake and I get to eat it too.
Although I'm not sure which I prefer, as I use both the on-screen and regular keyboard about equally, I think I'm a little faster with the regular keyboard.
But for a short text, sometimes it's more convenient to just use the on-screen.
Otherwise, I didn't find this article too worth-while.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430578</id>
	<title>Re:Bias?</title>
	<author>Wingsy</author>
	<datestamp>1268213760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Bingo! Been waiting for someone to point out the obvious flaw in this unscientific research.<br> <br>
The resident teen here types so fast on her iPhone that the feedback clicks sounds like a woodpecker. Once I asked to see what she had typed and saw no typos (but several abbreviations). Hand her a Blackberry and I'll guarantee that her results would be the opposite that obtained by the keyboard scientist.</htmltext>
<tokenext>Bingo !
Been waiting for someone to point out the obvious flaw in this unscientific research .
The resident teen here types so fast on her iPhone that the feedback clicks sounds like a woodpecker .
Once I asked to see what she had typed and saw no typos ( but several abbreviations ) .
Hand her a Blackberry and I 'll guarantee that her results would be the opposite that obtained by the keyboard scientist .</tokentext>
<sentencetext>Bingo!
Been waiting for someone to point out the obvious flaw in this unscientific research.
The resident teen here types so fast on her iPhone that the feedback clicks sounds like a woodpecker.
Once I asked to see what she had typed and saw no typos (but several abbreviations).
Hand her a Blackberry and I'll guarantee that her results would be the opposite that obtained by the keyboard scientist.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430420</id>
	<title>Real keyboard wanted!</title>
	<author>Geoffrey.landis</author>
	<datestamp>1268213040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I prefer not to have a keyboard on my smartphone because typing on a tiny keyboard, whether physical or not, is an enormous pain in the ass</p> </div><p>Yes-- complete agreement here.</p><p>What I really want is a full-size keyboard as a detachable accessory.  When I'm using the phone as just a phone, or for most simple browsing, I don't need to carry a keyboard around, but when I do need one, I'd like a full-sized one, not the little toys.</p><p>(It doesn't have to have all the useless keys that clutter up most computer keyboards these days-- just the old QWERTY ones.)</p></div>
	</htmltext>
<tokenext>I prefer not to have a keyboard on my smartphone because typing on a tiny keyboard , whether physical or not , is an enormous pain in the ass Yes-- complete agreement here.What I really want is a full-size keyboard as a detachable accessory .
When I 'm using the phone as just a phone , or for most simple browsing , I do n't need to carry a keyboard around , but when I do need one , I 'd like a full-sized one , not the little toys .
( It does n't have to have all the useless keys that clutter up most computer keyboards these days-- just the old QWERTY ones .
)</tokentext>
<sentencetext>I prefer not to have a keyboard on my smartphone because typing on a tiny keyboard, whether physical or not, is an enormous pain in the ass Yes-- complete agreement here.What I really want is a full-size keyboard as a detachable accessory.
When I'm using the phone as just a phone, or for most simple browsing, I don't need to carry a keyboard around, but when I do need one, I'd like a full-sized one, not the little toys.
(It doesn't have to have all the useless keys that clutter up most computer keyboards these days-- just the old QWERTY ones.
)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429864</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429910</id>
	<title>Blackberry</title>
	<author>physburn</author>
	<datestamp>1268253840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>  But doesn't it depend on the size of your fingers.
<p>
---
</p><p>
<a href="http://http//www.feeddistiller.com/blogs/Mobile\%20Phones/feed.html" title="http">Mobile Phone</a> [http] Feed @ <a href="http://www.feeddistiller.com/" title="feeddistiller.com">Feed Distiller</a> [feeddistiller.com]</p></htmltext>
<tokenext>But does n't it depend on the size of your fingers .
--- Mobile Phone [ http ] Feed @ Feed Distiller [ feeddistiller.com ]</tokentext>
<sentencetext>  But doesn't it depend on the size of your fingers.
---

Mobile Phone [http] Feed @ Feed Distiller [feeddistiller.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429956</id>
	<title>Re:Debate</title>
	<author>UnknowingFool</author>
	<datestamp>1268254020000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>There is tradeoff between screen size, keyboard size, phone size, durability, etc.  For users of a keyboardless phone like the iPhone, they get more screen and fewer moving parts.  However typing on them will be not as fast as with a hardware keyboard.  Each consumer should buy based on their individual needs.  For those that email and text a lot, a phone with a physical keyboard might be better.  For me, I don't email and text a lot so there will minimal downside to not having a physical keyboard.</htmltext>
<tokenext>There is tradeoff between screen size , keyboard size , phone size , durability , etc .
For users of a keyboardless phone like the iPhone , they get more screen and fewer moving parts .
However typing on them will be not as fast as with a hardware keyboard .
Each consumer should buy based on their individual needs .
For those that email and text a lot , a phone with a physical keyboard might be better .
For me , I do n't email and text a lot so there will minimal downside to not having a physical keyboard .</tokentext>
<sentencetext>There is tradeoff between screen size, keyboard size, phone size, durability, etc.
For users of a keyboardless phone like the iPhone, they get more screen and fewer moving parts.
However typing on them will be not as fast as with a hardware keyboard.
Each consumer should buy based on their individual needs.
For those that email and text a lot, a phone with a physical keyboard might be better.
For me, I don't email and text a lot so there will minimal downside to not having a physical keyboard.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430438</id>
	<title>Typos, awesome</title>
	<author>Anonymous</author>
	<datestamp>1268213100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"it&rsquo;s a debate that hotted up recently"</p><p>Normally I criticize the summaries for having typos, but this time the article itself has a pretty awesome one!</p></htmltext>
<tokenext>" it    s a debate that hotted up recently " Normally I criticize the summaries for having typos , but this time the article itself has a pretty awesome one !</tokentext>
<sentencetext>"it’s a debate that hotted up recently"Normally I criticize the summaries for having typos, but this time the article itself has a pretty awesome one!</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429950
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429956
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430420
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429864
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431070
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429916
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31433918
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429962
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430520
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429880
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31433444
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432572
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429910
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430716
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430578
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432044
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31434656
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31465250
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430568
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31439028
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430468
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429880
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_03_10_192224_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31435778
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430348
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430424
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429916
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31431070
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430458
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429874
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430578
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430716
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31434656
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430568
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430272
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430056
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31433918
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432516
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429848
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31465250
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31435778
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31439028
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31433444
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429964
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429806
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429956
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429950
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429962
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429864
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430420
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432044
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429880
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430520
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430468
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429910
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31432572
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31429876
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_03_10_192224.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_03_10_192224.31430252
</commentlist>
</conversation>
