<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_12_28_1424255</id>
	<title>Ruby In Practice</title>
	<author>samzenpus</author>
	<datestamp>1262025780000</datestamp>
	<htmltext>littleidea writes <i>"<em>Ruby In Practice</em> is like a sampler platter that picks up where <em>The Ruby Way</em> leaves off. Depending on your tastes each of the different offerings are delicious, but sometimes leave you wishing you had a whole order of just that. Then again, if you eat the whole thing, chances are you won't be hungry."</i> Keep reading for the rest of Andrew's review.</htmltext>
<tokenext>littleidea writes " Ruby In Practice is like a sampler platter that picks up where The Ruby Way leaves off .
Depending on your tastes each of the different offerings are delicious , but sometimes leave you wishing you had a whole order of just that .
Then again , if you eat the whole thing , chances are you wo n't be hungry .
" Keep reading for the rest of Andrew 's review .</tokentext>
<sentencetext>littleidea writes "Ruby In Practice is like a sampler platter that picks up where The Ruby Way leaves off.
Depending on your tastes each of the different offerings are delicious, but sometimes leave you wishing you had a whole order of just that.
Then again, if you eat the whole thing, chances are you won't be hungry.
" Keep reading for the rest of Andrew's review.</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576112</id>
	<title>Re:But is it (poignant)?</title>
	<author>Anonymous</author>
	<datestamp>1261996980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>More like whiney's poignant guide.</p></htmltext>
<tokenext>More like whiney 's poignant guide .</tokentext>
<sentencetext>More like whiney's poignant guide.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574020</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30580556</id>
	<title>Re:Ringing Endorsement</title>
	<author>Anonymous</author>
	<datestamp>1262086800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is one of the things in the book I had to do, so I give it a 10 for clear instructions and simplicity.</p></htmltext>
<tokenext>This is one of the things in the book I had to do , so I give it a 10 for clear instructions and simplicity .</tokentext>
<sentencetext>This is one of the things in the book I had to do, so I give it a 10 for clear instructions and simplicity.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574338</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574494</id>
	<title>'nuff said</title>
	<author>Jawn98685</author>
	<datestamp>1262031780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><nobr> <wbr></nobr></p><div class="quote"><p>...Ruby libraries change relatively quickly...</p></div><p>[shakes head]</p></div>
	</htmltext>
<tokenext>...Ruby libraries change relatively quickly... [ shakes head ]</tokentext>
<sentencetext> ...Ruby libraries change relatively quickly...[shakes head]
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30575080</id>
	<title>Re:More importantly...</title>
	<author>Anonymous</author>
	<datestamp>1261991820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The way gems with native libraries are implemented has been (and still is in 1.9) a major weakness in Ruby.  The module API exposes far too much of the inner workings of Ruby.  There is a growing movement to change these gems to use FFI instead of wrapping the native API in a Ruby C module.  This allows the gem to be pure ruby and call out to the native library, which in turn would make the gem much more portable, not only between ruby version, but also between different Ruby implementations.</p></htmltext>
<tokenext>The way gems with native libraries are implemented has been ( and still is in 1.9 ) a major weakness in Ruby .
The module API exposes far too much of the inner workings of Ruby .
There is a growing movement to change these gems to use FFI instead of wrapping the native API in a Ruby C module .
This allows the gem to be pure ruby and call out to the native library , which in turn would make the gem much more portable , not only between ruby version , but also between different Ruby implementations .</tokentext>
<sentencetext>The way gems with native libraries are implemented has been (and still is in 1.9) a major weakness in Ruby.
The module API exposes far too much of the inner workings of Ruby.
There is a growing movement to change these gems to use FFI instead of wrapping the native API in a Ruby C module.
This allows the gem to be pure ruby and call out to the native library, which in turn would make the gem much more portable, not only between ruby version, but also between different Ruby implementations.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574638</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576120</id>
	<title>Hi, the author here...</title>
	<author>Anonymous</author>
	<datestamp>1261996980000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Looks like the stock is getting slim over on Amazon, so if you want to order it still and they're out, hit up the Manning site: <a href="http://manning.com/mcanally/" title="manning.com" rel="nofollow">http://manning.com/mcanally/</a> [manning.com]

Thanks!</htmltext>
<tokenext>Looks like the stock is getting slim over on Amazon , so if you want to order it still and they 're out , hit up the Manning site : http : //manning.com/mcanally/ [ manning.com ] Thanks !</tokentext>
<sentencetext>Looks like the stock is getting slim over on Amazon, so if you want to order it still and they're out, hit up the Manning site: http://manning.com/mcanally/ [manning.com]

Thanks!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574638</id>
	<title>Re:More importantly...</title>
	<author>steveb3210</author>
	<datestamp>1262032560000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Ruby 1.9 moved to a VM architecture and with a sizable performance boost.  unfortunately they also managed to break half the existing gems out there with changes to the language; slowly but surely things are moving in the right direction.</htmltext>
<tokenext>Ruby 1.9 moved to a VM architecture and with a sizable performance boost .
unfortunately they also managed to break half the existing gems out there with changes to the language ; slowly but surely things are moving in the right direction .</tokentext>
<sentencetext>Ruby 1.9 moved to a VM architecture and with a sizable performance boost.
unfortunately they also managed to break half the existing gems out there with changes to the language; slowly but surely things are moving in the right direction.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574520</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574184</id>
	<title>yawn</title>
	<author>Anonymous</author>
	<datestamp>1262030340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>[ ] newsworthy</htmltext>
<tokenext>[ ] newsworthy</tokentext>
<sentencetext>[ ] newsworthy</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574020</id>
	<title>But is it (poignant)?</title>
	<author>Anonymous</author>
	<datestamp>1262029620000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>Still my favorite:<br>why's (poignant) guide to ruby  <a href="http://mislav.uniqpath.com/poignant-guide/book/" title="uniqpath.com">http://mislav.uniqpath.com/poignant-guide/book/</a> [uniqpath.com]</p></htmltext>
<tokenext>Still my favorite : why 's ( poignant ) guide to ruby http : //mislav.uniqpath.com/poignant-guide/book/ [ uniqpath.com ]</tokentext>
<sentencetext>Still my favorite:why's (poignant) guide to ruby  http://mislav.uniqpath.com/poignant-guide/book/ [uniqpath.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30670786</id>
	<title>Re:Before commenting, please complete this form</title>
	<author>chris44larsen</author>
	<datestamp>1231262220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>[ xxx] I already have a positive/negative entrenched opinion of Python or Ruby

[xxx ] I assume Ruby == Ruby on Rails

[xxx ] I program in PHP for it's robust design, consistent syntax and architectural soundness<nobr> <wbr></nobr>:)</htmltext>
<tokenext>[ xxx ] I already have a positive/negative entrenched opinion of Python or Ruby [ xxx ] I assume Ruby = = Ruby on Rails [ xxx ] I program in PHP for it 's robust design , consistent syntax and architectural soundness : )</tokentext>
<sentencetext>[ xxx] I already have a positive/negative entrenched opinion of Python or Ruby

[xxx ] I assume Ruby == Ruby on Rails

[xxx ] I program in PHP for it's robust design, consistent syntax and architectural soundness :)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574540</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30578144</id>
	<title>Re:More importantly...</title>
	<author>Anonymous</author>
	<datestamp>1262011860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>.<br>Python, Perl or other Scripting languages where there is little optimization that can go on as the code is running as it interprets the next line of code.</p></div><p>Python is automatically compiled to portable byte code, and perl (and most other scripting languages) is not interpreted line-by-line.</p></div>
	</htmltext>
<tokenext>.Python , Perl or other Scripting languages where there is little optimization that can go on as the code is running as it interprets the next line of code.Python is automatically compiled to portable byte code , and perl ( and most other scripting languages ) is not interpreted line-by-line .</tokentext>
<sentencetext>.Python, Perl or other Scripting languages where there is little optimization that can go on as the code is running as it interprets the next line of code.Python is automatically compiled to portable byte code, and perl (and most other scripting languages) is not interpreted line-by-line.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574750</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576464</id>
	<title>Really need a book on scaling ruby on rails</title>
	<author>fortapocalypse</author>
	<datestamp>1261998960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If there were a good book on how to (more easily) scale ruby/jruby on rails apps, I'd buy it. I don't think I'd buy a book on Ruby otherwise.</htmltext>
<tokenext>If there were a good book on how to ( more easily ) scale ruby/jruby on rails apps , I 'd buy it .
I do n't think I 'd buy a book on Ruby otherwise .</tokentext>
<sentencetext>If there were a good book on how to (more easily) scale ruby/jruby on rails apps, I'd buy it.
I don't think I'd buy a book on Ruby otherwise.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574834</id>
	<title>Re:Awesome</title>
	<author>bberens</author>
	<datestamp>1262033700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The same was true for Java in its early days and now it's quite fast.  I'm no Ruby fan, but I am confident that it will get over its speed issues in time.  It's definitely an up-and-comer.  Personally I'm pulling for Groovy and GRAILS, but I don't think it'll ever get past being a knockoff.</htmltext>
<tokenext>The same was true for Java in its early days and now it 's quite fast .
I 'm no Ruby fan , but I am confident that it will get over its speed issues in time .
It 's definitely an up-and-comer .
Personally I 'm pulling for Groovy and GRAILS , but I do n't think it 'll ever get past being a knockoff .</tokentext>
<sentencetext>The same was true for Java in its early days and now it's quite fast.
I'm no Ruby fan, but I am confident that it will get over its speed issues in time.
It's definitely an up-and-comer.
Personally I'm pulling for Groovy and GRAILS, but I don't think it'll ever get past being a knockoff.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574164</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544</id>
	<title>Who wants Ruby?</title>
	<author>GooberToo</author>
	<datestamp>1261999500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I really never figured out exactly who Ruby appeals to. It seems those who would be interested in Ruby would also be attracted by the more mature Python.</p><p>So what projects and for what reasons are people picking Ruby over Python? Perhaps Python isn't even in the comparison? Is it just to be different? The antithesis of the heard mentality? Some critical feature Python is missing? Superior frameworks? Why?</p></htmltext>
<tokenext>I really never figured out exactly who Ruby appeals to .
It seems those who would be interested in Ruby would also be attracted by the more mature Python.So what projects and for what reasons are people picking Ruby over Python ?
Perhaps Python is n't even in the comparison ?
Is it just to be different ?
The antithesis of the heard mentality ?
Some critical feature Python is missing ?
Superior frameworks ?
Why ?</tokentext>
<sentencetext>I really never figured out exactly who Ruby appeals to.
It seems those who would be interested in Ruby would also be attracted by the more mature Python.So what projects and for what reasons are people picking Ruby over Python?
Perhaps Python isn't even in the comparison?
Is it just to be different?
The antithesis of the heard mentality?
Some critical feature Python is missing?
Superior frameworks?
Why?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574848</id>
	<title>Re:Awesome</title>
	<author>Anonymous</author>
	<datestamp>1262033760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>For the record, ruby 1.9 is on par with python, speed wise.</p></htmltext>
<tokenext>For the record , ruby 1.9 is on par with python , speed wise .</tokentext>
<sentencetext>For the record, ruby 1.9 is on par with python, speed wise.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574164</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574338</id>
	<title>Ringing Endorsement</title>
	<author>Anonymous</author>
	<datestamp>1262031060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>"[If] you need to hook up your jabber server to a message queue that will spawn workers that interact with RESTful web services exposing indexed logs to twitter by tomorrow, then this book is a 10."</p><p>I think you have comprehensively explained why I don't want to read this book.</p><p>Thank you sir, for your service to humanity!</p></htmltext>
<tokenext>" [ If ] you need to hook up your jabber server to a message queue that will spawn workers that interact with RESTful web services exposing indexed logs to twitter by tomorrow , then this book is a 10 .
" I think you have comprehensively explained why I do n't want to read this book.Thank you sir , for your service to humanity !</tokentext>
<sentencetext>"[If] you need to hook up your jabber server to a message queue that will spawn workers that interact with RESTful web services exposing indexed logs to twitter by tomorrow, then this book is a 10.
"I think you have comprehensively explained why I don't want to read this book.Thank you sir, for your service to humanity!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30584540</id>
	<title>Re:Groovy/Griffon/Grails</title>
	<author>mgkimsal2</author>
	<datestamp>1262115180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We at <a href="http://groovymag.com/" title="groovymag.com">http://groovymag.com/</a> [groovymag.com] are trying to help with the recognition bit, although it does at times feel a bit like an uphill battle<nobr> <wbr></nobr>;)</htmltext>
<tokenext>We at http : //groovymag.com/ [ groovymag.com ] are trying to help with the recognition bit , although it does at times feel a bit like an uphill battle ; )</tokentext>
<sentencetext>We at http://groovymag.com/ [groovymag.com] are trying to help with the recognition bit, although it does at times feel a bit like an uphill battle ;)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30575388</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30577142</id>
	<title>Re:Who wants Ruby?</title>
	<author>Anonymous</author>
	<datestamp>1262003820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>It seems those who would be interested in Ruby would also be attracted by the more mature Python.</p></div><p>Very often the reverse is true.  I was attracted to Python, learned it, loved it (I still quite like it). Then I met Ruby.  Of the two, I prefer Ruby.</p></div>
	</htmltext>
<tokenext>It seems those who would be interested in Ruby would also be attracted by the more mature Python.Very often the reverse is true .
I was attracted to Python , learned it , loved it ( I still quite like it ) .
Then I met Ruby .
Of the two , I prefer Ruby .</tokentext>
<sentencetext>It seems those who would be interested in Ruby would also be attracted by the more mature Python.Very often the reverse is true.
I was attracted to Python, learned it, loved it (I still quite like it).
Then I met Ruby.
Of the two, I prefer Ruby.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30670820</id>
	<title>Re:Who wants Ruby?</title>
	<author>chris44larsen</author>
	<datestamp>1231262340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>true, but python is far from perfect..........</htmltext>
<tokenext>true , but python is far from perfect......... .</tokentext>
<sentencetext>true, but python is far from perfect..........</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574346</id>
	<title>Yeah, I remember ...</title>
	<author>neonprimetime</author>
	<datestamp>1262031120000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>... <a href="http://www.imdb.com/title/tt0108002/" title="imdb.com">Rudy</a> [imdb.com], he always practiced real hard, a real die hard<nobr> <wbr></nobr>... but I don't recall if he ever got to play in any actual games.</htmltext>
<tokenext>... Rudy [ imdb.com ] , he always practiced real hard , a real die hard ... but I do n't recall if he ever got to play in any actual games .</tokentext>
<sentencetext>... Rudy [imdb.com], he always practiced real hard, a real die hard ... but I don't recall if he ever got to play in any actual games.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30585336</id>
	<title>Re:Who wants Ruby?</title>
	<author>DragonWriter</author>
	<datestamp>1262118900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>I really never figured out exactly who Ruby appeals to. It seems those who would be interested in Ruby would also be attracted by the more mature Python.</p></div></blockquote><p>Lots of Rubyists are also attracted by Python, though even many of those that like Python in general often dislike particular aspects of Python (the whitespace handling is a big one.) Also, lots of people prefer Ruby because they like particular Ruby frameworks (Rails, of course, is a big one) or because they found it an easier transition from Perl. And lots of people have particular features that make them prefer Ruby (blocks are the one I've seen cited most often.)</p></div>
	</htmltext>
<tokenext>I really never figured out exactly who Ruby appeals to .
It seems those who would be interested in Ruby would also be attracted by the more mature Python.Lots of Rubyists are also attracted by Python , though even many of those that like Python in general often dislike particular aspects of Python ( the whitespace handling is a big one .
) Also , lots of people prefer Ruby because they like particular Ruby frameworks ( Rails , of course , is a big one ) or because they found it an easier transition from Perl .
And lots of people have particular features that make them prefer Ruby ( blocks are the one I 've seen cited most often .
)</tokentext>
<sentencetext>I really never figured out exactly who Ruby appeals to.
It seems those who would be interested in Ruby would also be attracted by the more mature Python.Lots of Rubyists are also attracted by Python, though even many of those that like Python in general often dislike particular aspects of Python (the whitespace handling is a big one.
) Also, lots of people prefer Ruby because they like particular Ruby frameworks (Rails, of course, is a big one) or because they found it an easier transition from Perl.
And lots of people have particular features that make them prefer Ruby (blocks are the one I've seen cited most often.
)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574880</id>
	<title>Good News / Bad News</title>
	<author>vlm</author>
	<datestamp>1261990800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The good news, is I like the topic, I have fat stacks of cash and am willing to part with it for a good book.  Emphasis on the word Good.  A direct pipeline into the minds of the insiders, is worth some bucks.</p><p><div class="quote"><p>The book credits a number of Rubyists with contributions for each of the sections.</p></div><p>Ah, and then the bad news.  Naughty book editor, gimme my money back.</p><p><div class="quote"><p>This makes for some noticeable variation in the stylistic presentation from topic to topic.</p></div><p>So, Mr reviewer, what say?  You described the battlefield, now which side won?  Do the direct insights of the words of the prophets outweigh cruddy editing, or is it too shaky to read?  I've got a pocket full of cash and like the bank robber says in the movie Dirty Harry, indecisively struggling asking himself if Harry's revolver is empty or not, "... I gots to know<nobr> <wbr></nobr>..."</p></div>
	</htmltext>
<tokenext>The good news , is I like the topic , I have fat stacks of cash and am willing to part with it for a good book .
Emphasis on the word Good .
A direct pipeline into the minds of the insiders , is worth some bucks.The book credits a number of Rubyists with contributions for each of the sections.Ah , and then the bad news .
Naughty book editor , gim me my money back.This makes for some noticeable variation in the stylistic presentation from topic to topic.So , Mr reviewer , what say ?
You described the battlefield , now which side won ?
Do the direct insights of the words of the prophets outweigh cruddy editing , or is it too shaky to read ?
I 've got a pocket full of cash and like the bank robber says in the movie Dirty Harry , indecisively struggling asking himself if Harry 's revolver is empty or not , " ... I gots to know ... "</tokentext>
<sentencetext>The good news, is I like the topic, I have fat stacks of cash and am willing to part with it for a good book.
Emphasis on the word Good.
A direct pipeline into the minds of the insiders, is worth some bucks.The book credits a number of Rubyists with contributions for each of the sections.Ah, and then the bad news.
Naughty book editor, gimme my money back.This makes for some noticeable variation in the stylistic presentation from topic to topic.So, Mr reviewer, what say?
You described the battlefield, now which side won?
Do the direct insights of the words of the prophets outweigh cruddy editing, or is it too shaky to read?
I've got a pocket full of cash and like the bank robber says in the movie Dirty Harry, indecisively struggling asking himself if Harry's revolver is empty or not, "... I gots to know ..."
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30671598</id>
	<title>Re:Who wants Ruby?</title>
	<author>chris44larsen</author>
	<datestamp>1231265340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Who like ruby? Those that get frustrated by Python and think that it is way too high level.</htmltext>
<tokenext>Who like ruby ?
Those that get frustrated by Python and think that it is way too high level .</tokentext>
<sentencetext>Who like ruby?
Those that get frustrated by Python and think that it is way too high level.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574520</id>
	<title>More importantly...</title>
	<author>LOLLinux</author>
	<datestamp>1262031960000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>have they fixed the problem of Ruby being slow as shit?</p></htmltext>
<tokenext>have they fixed the problem of Ruby being slow as shit ?</tokentext>
<sentencetext>have they fixed the problem of Ruby being slow as shit?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30708772</id>
	<title>Sunny</title>
	<author>Anonymous</author>
	<datestamp>1231530900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>To many nerds here. <a href="http://padabum.com/" title="padabum.com" rel="nofollow">Go relax</a> [padabum.com]</htmltext>
<tokenext>To many nerds here .
Go relax [ padabum.com ]</tokentext>
<sentencetext>To many nerds here.
Go relax [padabum.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574866</id>
	<title>McAnally?</title>
	<author>Anonymous</author>
	<datestamp>1262033880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Google trends:</p><p><a href="http://tinyurl.com/rubypython" title="tinyurl.com" rel="nofollow">http://tinyurl.com/rubypython</a> [tinyurl.com]</p></htmltext>
<tokenext>Google trends : http : //tinyurl.com/rubypython [ tinyurl.com ]</tokentext>
<sentencetext>Google trends:http://tinyurl.com/rubypython [tinyurl.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30582354</id>
	<title>Re:Who wants Ruby?</title>
	<author>mcvos</author>
	<datestamp>1262104320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The only meaningful distinction I've seen after spending time investigating the two and why some choose one over the other, is the underlying philosophy of each.  With Python, there's almost always a "right" way to do a particular thing, an attitude of choosing the best practice summed up in the adjective "pythonic".  Ruby follows Perl's TIMTOWTDI line, with a very flexible syntax that allows for a variety of ways to accomplish a particular end.  So mainly, it's a temperament thing:  coders who like a flexible tool that allows them to find 'clever' solutions prefer Ruby; coders (like me) who like for there to be a best practice, and don't break the rules without a decent reason to do so, prefer python.</p></div><p>This is a very good point. This also shines through in the culture of the communities. I've read from several people that they got annoyed by the Python community's rigid stance. Often someone would find an odd quirk (arguably even a bug) in Python and ask why it was like that. Instead of responding with possible fixes, the responses often amounted to "that's the only right way to do it, and if you disagree, you're wrong" (though probably phrased more diplomatically). In many other communities (including Ruby), the response is more likely to be something like "yeah, we need to fix that some day", "there's a plugin/gem for that" or "here's how you can fix that yourself".</p><p><div class="quote"><p>A good snapshot of the difference was in Zed Shaw's now disappeared rant about Ruby, where what set him off was finding a bunch of hacks injected into a logging library he was using, and realizing that he was not only going to have to inject his own, but that this was expected and commended in the community.  The idea that there should be a stable API forming the basis of a contract with the programmer was looked down upon by Rubyists, causing Shaw to dismiss them as cowboys and amateurs.</p></div><p>Valid criticism. Ruby is often more hacky, and there are a lot of issues that do need to get fixed some day. Then again, people generally do recognise them as broken and do plan to fix them, rather than claiming it's the way God intended it.</p></div>
	</htmltext>
<tokenext>The only meaningful distinction I 've seen after spending time investigating the two and why some choose one over the other , is the underlying philosophy of each .
With Python , there 's almost always a " right " way to do a particular thing , an attitude of choosing the best practice summed up in the adjective " pythonic " .
Ruby follows Perl 's TIMTOWTDI line , with a very flexible syntax that allows for a variety of ways to accomplish a particular end .
So mainly , it 's a temperament thing : coders who like a flexible tool that allows them to find 'clever ' solutions prefer Ruby ; coders ( like me ) who like for there to be a best practice , and do n't break the rules without a decent reason to do so , prefer python.This is a very good point .
This also shines through in the culture of the communities .
I 've read from several people that they got annoyed by the Python community 's rigid stance .
Often someone would find an odd quirk ( arguably even a bug ) in Python and ask why it was like that .
Instead of responding with possible fixes , the responses often amounted to " that 's the only right way to do it , and if you disagree , you 're wrong " ( though probably phrased more diplomatically ) .
In many other communities ( including Ruby ) , the response is more likely to be something like " yeah , we need to fix that some day " , " there 's a plugin/gem for that " or " here 's how you can fix that yourself " .A good snapshot of the difference was in Zed Shaw 's now disappeared rant about Ruby , where what set him off was finding a bunch of hacks injected into a logging library he was using , and realizing that he was not only going to have to inject his own , but that this was expected and commended in the community .
The idea that there should be a stable API forming the basis of a contract with the programmer was looked down upon by Rubyists , causing Shaw to dismiss them as cowboys and amateurs.Valid criticism .
Ruby is often more hacky , and there are a lot of issues that do need to get fixed some day .
Then again , people generally do recognise them as broken and do plan to fix them , rather than claiming it 's the way God intended it .</tokentext>
<sentencetext>The only meaningful distinction I've seen after spending time investigating the two and why some choose one over the other, is the underlying philosophy of each.
With Python, there's almost always a "right" way to do a particular thing, an attitude of choosing the best practice summed up in the adjective "pythonic".
Ruby follows Perl's TIMTOWTDI line, with a very flexible syntax that allows for a variety of ways to accomplish a particular end.
So mainly, it's a temperament thing:  coders who like a flexible tool that allows them to find 'clever' solutions prefer Ruby; coders (like me) who like for there to be a best practice, and don't break the rules without a decent reason to do so, prefer python.This is a very good point.
This also shines through in the culture of the communities.
I've read from several people that they got annoyed by the Python community's rigid stance.
Often someone would find an odd quirk (arguably even a bug) in Python and ask why it was like that.
Instead of responding with possible fixes, the responses often amounted to "that's the only right way to do it, and if you disagree, you're wrong" (though probably phrased more diplomatically).
In many other communities (including Ruby), the response is more likely to be something like "yeah, we need to fix that some day", "there's a plugin/gem for that" or "here's how you can fix that yourself".A good snapshot of the difference was in Zed Shaw's now disappeared rant about Ruby, where what set him off was finding a bunch of hacks injected into a logging library he was using, and realizing that he was not only going to have to inject his own, but that this was expected and commended in the community.
The idea that there should be a stable API forming the basis of a contract with the programmer was looked down upon by Rubyists, causing Shaw to dismiss them as cowboys and amateurs.Valid criticism.
Ruby is often more hacky, and there are a lot of issues that do need to get fixed some day.
Then again, people generally do recognise them as broken and do plan to fix them, rather than claiming it's the way God intended it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30580052</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30575388</id>
	<title>Groovy/Griffon/Grails</title>
	<author>Foofoobar</author>
	<datestamp>1261993260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Gotta second that. I liked Ruby but hated the speed and scalability issues. Beginning to loathe PHP because of its inconsistencies and inability to advance the language.<br> <br>

Groovy on the other hand has a community that is advancing (without much recognition) a rich platform with Grails (for web apps) and Griffon (for swing apps). It's amazingly fast, simple and easy and integrates with traditional Java without any additional configuration needs. This will definitely kill JRuby for the most part.</htmltext>
<tokenext>Got ta second that .
I liked Ruby but hated the speed and scalability issues .
Beginning to loathe PHP because of its inconsistencies and inability to advance the language .
Groovy on the other hand has a community that is advancing ( without much recognition ) a rich platform with Grails ( for web apps ) and Griffon ( for swing apps ) .
It 's amazingly fast , simple and easy and integrates with traditional Java without any additional configuration needs .
This will definitely kill JRuby for the most part .</tokentext>
<sentencetext>Gotta second that.
I liked Ruby but hated the speed and scalability issues.
Beginning to loathe PHP because of its inconsistencies and inability to advance the language.
Groovy on the other hand has a community that is advancing (without much recognition) a rich platform with Grails (for web apps) and Griffon (for swing apps).
It's amazingly fast, simple and easy and integrates with traditional Java without any additional configuration needs.
This will definitely kill JRuby for the most part.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574834</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574006</id>
	<title>Too many words</title>
	<author>Anonymous</author>
	<datestamp>1262029560000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p>And that dude's hat is scaring me.</p></htmltext>
<tokenext>And that dude 's hat is scaring me .</tokentext>
<sentencetext>And that dude's hat is scaring me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30580052</id>
	<title>Re:Who wants Ruby?</title>
	<author>jjohnson</author>
	<datestamp>1262077440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The only meaningful distinction I've seen after spending time investigating the two and why some choose one over the other, is the underlying philosophy of each.  With Python, there's almost always a "right" way to do a particular thing, an attitude of choosing the best practice summed up in the adjective "pythonic".  Ruby follows Perl's TIMTOWTDI line, with a very flexible syntax that allows for a variety of ways to accomplish a particular end.  So mainly, it's a temperament thing:  coders who like a flexible tool that allows them to find 'clever' solutions prefer Ruby; coders (like me) who like for there to be a best practice, and don't break the rules without a decent reason to do so, prefer python.</p><p>A good snapshot of the difference was in Zed Shaw's now disappeared rant about Ruby, where what set him off was finding a bunch of hacks injected into a logging library he was using, and realizing that he was not only going to have to inject his own, but that this was expected and commended in the community.  The idea that there should be a stable API forming the basis of a contract with the programmer was looked down upon by Rubyists, causing Shaw to dismiss them as cowboys and amateurs.</p></htmltext>
<tokenext>The only meaningful distinction I 've seen after spending time investigating the two and why some choose one over the other , is the underlying philosophy of each .
With Python , there 's almost always a " right " way to do a particular thing , an attitude of choosing the best practice summed up in the adjective " pythonic " .
Ruby follows Perl 's TIMTOWTDI line , with a very flexible syntax that allows for a variety of ways to accomplish a particular end .
So mainly , it 's a temperament thing : coders who like a flexible tool that allows them to find 'clever ' solutions prefer Ruby ; coders ( like me ) who like for there to be a best practice , and do n't break the rules without a decent reason to do so , prefer python.A good snapshot of the difference was in Zed Shaw 's now disappeared rant about Ruby , where what set him off was finding a bunch of hacks injected into a logging library he was using , and realizing that he was not only going to have to inject his own , but that this was expected and commended in the community .
The idea that there should be a stable API forming the basis of a contract with the programmer was looked down upon by Rubyists , causing Shaw to dismiss them as cowboys and amateurs .</tokentext>
<sentencetext>The only meaningful distinction I've seen after spending time investigating the two and why some choose one over the other, is the underlying philosophy of each.
With Python, there's almost always a "right" way to do a particular thing, an attitude of choosing the best practice summed up in the adjective "pythonic".
Ruby follows Perl's TIMTOWTDI line, with a very flexible syntax that allows for a variety of ways to accomplish a particular end.
So mainly, it's a temperament thing:  coders who like a flexible tool that allows them to find 'clever' solutions prefer Ruby; coders (like me) who like for there to be a best practice, and don't break the rules without a decent reason to do so, prefer python.A good snapshot of the difference was in Zed Shaw's now disappeared rant about Ruby, where what set him off was finding a bunch of hacks injected into a logging library he was using, and realizing that he was not only going to have to inject his own, but that this was expected and commended in the community.
The idea that there should be a stable API forming the basis of a contract with the programmer was looked down upon by Rubyists, causing Shaw to dismiss them as cowboys and amateurs.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30573986</id>
	<title>Ruby</title>
	<author>Anonymous</author>
	<datestamp>1262029440000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Did they get rid of that whitespace crap yet?</p></htmltext>
<tokenext>Did they get rid of that whitespace crap yet ?</tokentext>
<sentencetext>Did they get rid of that whitespace crap yet?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574542</id>
	<title>Re:Ruby</title>
	<author>Anonymous</author>
	<datestamp>1262032080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Why mess with Ruby at all?  Just use a real language such as VisualBasic.NET.</p></htmltext>
<tokenext>Why mess with Ruby at all ?
Just use a real language such as VisualBasic.NET .</tokentext>
<sentencetext>Why mess with Ruby at all?
Just use a real language such as VisualBasic.NET.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30573986</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574048</id>
	<title>Awesome</title>
	<author>Anonymous</author>
	<datestamp>1262029800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>  I  highly recommend this book.  There are so many amazing things one can do with ruby, and knowing them can save a lot of time and make the code easier to read too.</htmltext>
<tokenext>I highly recommend this book .
There are so many amazing things one can do with ruby , and knowing them can save a lot of time and make the code easier to read too .</tokentext>
<sentencetext>  I  highly recommend this book.
There are so many amazing things one can do with ruby, and knowing them can save a lot of time and make the code easier to read too.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574464</id>
	<title>Why buy it?</title>
	<author>vlm</author>
	<datestamp>1262031720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>There were a few gem updates which were not compatible with the code in the book. The twitter gem in particular had non-backward compatible changes to authentication (to support OAuth). I was able to get the example working with a few minutes of Google</p></div><p>Time for my usual Slashdot book review rant.  Why buy this book, if the review states its mostly a list of inspirational google searches?</p><p>MOST technical books are little more than edited concatenated google searches... However it is possible to write a technical book that is better than that, or at least different from that.  For example, the "little schemer" series is certainly unique.</p><p>So, why buy this book?</p></div>
	</htmltext>
<tokenext>There were a few gem updates which were not compatible with the code in the book .
The twitter gem in particular had non-backward compatible changes to authentication ( to support OAuth ) .
I was able to get the example working with a few minutes of GoogleTime for my usual Slashdot book review rant .
Why buy this book , if the review states its mostly a list of inspirational google searches ? MOST technical books are little more than edited concatenated google searches... However it is possible to write a technical book that is better than that , or at least different from that .
For example , the " little schemer " series is certainly unique.So , why buy this book ?</tokentext>
<sentencetext>There were a few gem updates which were not compatible with the code in the book.
The twitter gem in particular had non-backward compatible changes to authentication (to support OAuth).
I was able to get the example working with a few minutes of GoogleTime for my usual Slashdot book review rant.
Why buy this book, if the review states its mostly a list of inspirational google searches?MOST technical books are little more than edited concatenated google searches... However it is possible to write a technical book that is better than that, or at least different from that.
For example, the "little schemer" series is certainly unique.So, why buy this book?
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574164</id>
	<title>Re:Awesome</title>
	<author>Anonymous</author>
	<datestamp>1262030220000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>There are so many amazing things one can do with ruby,</p></div><p>Yeah like making a server run like a 386 due to bloaty, slow code like Ruby on Rails.</p></div>
	</htmltext>
<tokenext>There are so many amazing things one can do with ruby,Yeah like making a server run like a 386 due to bloaty , slow code like Ruby on Rails .</tokentext>
<sentencetext>There are so many amazing things one can do with ruby,Yeah like making a server run like a 386 due to bloaty, slow code like Ruby on Rails.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574048</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574276</id>
	<title>Frightening title</title>
	<author>bluefoxlucid</author>
	<datestamp>1262030820000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>"Ruby in Practice" makes me imagine a book filled with code samples of a modified, human-readable version of Brainfuck.</p></htmltext>
<tokenext>" Ruby in Practice " makes me imagine a book filled with code samples of a modified , human-readable version of Brainfuck .</tokentext>
<sentencetext>"Ruby in Practice" makes me imagine a book filled with code samples of a modified, human-readable version of Brainfuck.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30578472</id>
	<title>Every Language I've Ever Worked With...</title>
	<author>Anonymous</author>
	<datestamp>1262014320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Has Pros and Cons but I'm more productive with Ruby than with any other language.</p><p>Sure, there's a learning curve and you have to take the time to explore the libraries but the same can be said<br>for every other language I've ever worked with (going on 18+ at point).</p><p>The language is still undergoing development and experimentation is a vital part of that process. Language lawyers,<br>conservatives, structuralists and retired-on-the-job beware! Thinking and investigation are required.</p><p>That said, the bottom line is still that I get more done and that's most important to me.</p></htmltext>
<tokenext>Has Pros and Cons but I 'm more productive with Ruby than with any other language.Sure , there 's a learning curve and you have to take the time to explore the libraries but the same can be saidfor every other language I 've ever worked with ( going on 18 + at point ) .The language is still undergoing development and experimentation is a vital part of that process .
Language lawyers,conservatives , structuralists and retired-on-the-job beware !
Thinking and investigation are required.That said , the bottom line is still that I get more done and that 's most important to me .</tokentext>
<sentencetext>Has Pros and Cons but I'm more productive with Ruby than with any other language.Sure, there's a learning curve and you have to take the time to explore the libraries but the same can be saidfor every other language I've ever worked with (going on 18+ at point).The language is still undergoing development and experimentation is a vital part of that process.
Language lawyers,conservatives, structuralists and retired-on-the-job beware!
Thinking and investigation are required.That said, the bottom line is still that I get more done and that's most important to me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574692</id>
	<title>Ruby on Rails is for primadonnas</title>
	<author>Anonymous</author>
	<datestamp>1262032860000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Ruby on Rails is for primadonnas who think their bloated one size fits all framework is the answer to the problem before they even hear the solution.</p><p>Their zealotry is best understood when you realize that since they aren't real programmers to begin with, this is the only option available to them. It's easier to badmouth all other languages than it is to fully learn a single language.</p></htmltext>
<tokenext>Ruby on Rails is for primadonnas who think their bloated one size fits all framework is the answer to the problem before they even hear the solution.Their zealotry is best understood when you realize that since they are n't real programmers to begin with , this is the only option available to them .
It 's easier to badmouth all other languages than it is to fully learn a single language .</tokentext>
<sentencetext>Ruby on Rails is for primadonnas who think their bloated one size fits all framework is the answer to the problem before they even hear the solution.Their zealotry is best understood when you realize that since they aren't real programmers to begin with, this is the only option available to them.
It's easier to badmouth all other languages than it is to fully learn a single language.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574252</id>
	<title>PIZZA ANALOGY</title>
	<author>Anonymous</author>
	<datestamp>1262030700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>What a great opportunity for a pizza analogy!<br> <br>Anybody got one?</htmltext>
<tokenext>What a great opportunity for a pizza analogy !
Anybody got one ?</tokentext>
<sentencetext>What a great opportunity for a pizza analogy!
Anybody got one?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574382</id>
	<title>To summarize:</title>
	<author>Anonymous</author>
	<datestamp>1262031240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"Depending on your tastes each of the different offerings are delicious, but sometimes leave you wishing you had a whole order of just that. Then again, if you eat the whole thing, chances are you won't be hungry. You need to hook up your jabber server to a message queue that will spawn workers that interact with RESTful web services exposing indexed logs to twitter!! That being said, you don't need to understand the subtleties of 'yield' or 'inject' to understand Rails!"</p></htmltext>
<tokenext>" Depending on your tastes each of the different offerings are delicious , but sometimes leave you wishing you had a whole order of just that .
Then again , if you eat the whole thing , chances are you wo n't be hungry .
You need to hook up your jabber server to a message queue that will spawn workers that interact with RESTful web services exposing indexed logs to twitter ! !
That being said , you do n't need to understand the subtleties of 'yield ' or 'inject ' to understand Rails !
"</tokentext>
<sentencetext>"Depending on your tastes each of the different offerings are delicious, but sometimes leave you wishing you had a whole order of just that.
Then again, if you eat the whole thing, chances are you won't be hungry.
You need to hook up your jabber server to a message queue that will spawn workers that interact with RESTful web services exposing indexed logs to twitter!!
That being said, you don't need to understand the subtleties of 'yield' or 'inject' to understand Rails!
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30590134</id>
	<title>Re:Who wants Ruby?</title>
	<author>Anonymous</author>
	<datestamp>1262103000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I Just took a Ruby job, after spending the last 5 years doing Python.</p><p>Python is excellent because of it's maturity. Ruby is excellent because of it's modernity.</p><p>To use a metaphor, it's like the difference between dating a 35 year old career woman vs a 20 year old college girl. The former is set in her ways and will offer a stable relationship with a lot of benefits. The latter is full of potential and can teach you new tricks.</p><p>In practical terms, Ruby happens to have a lot of programmers trying to change *how* software is written. The 3rd party library and distribution eco-system (gems via gemcutter, rubyforge, github) is better than any other language. Rack and Sinatra are easier and cleaner than WSGI and what, web.py? Finally the Heroku platform is *incomparable*.</p><p>So yes, frameworks and platforms are a big part of the appeal of Ruby over Python these days.</p><p>As for why Ruby might be doing better here? For one, Ruby is a more expressive than Python, and better designed than Perl; it does have features other languages are missing. For two, Ruby hit the scene after computers and the web were ubiquitous so it's just good circumstance for something new, and perhaps better, to catch on.</p></htmltext>
<tokenext>I Just took a Ruby job , after spending the last 5 years doing Python.Python is excellent because of it 's maturity .
Ruby is excellent because of it 's modernity.To use a metaphor , it 's like the difference between dating a 35 year old career woman vs a 20 year old college girl .
The former is set in her ways and will offer a stable relationship with a lot of benefits .
The latter is full of potential and can teach you new tricks.In practical terms , Ruby happens to have a lot of programmers trying to change * how * software is written .
The 3rd party library and distribution eco-system ( gems via gemcutter , rubyforge , github ) is better than any other language .
Rack and Sinatra are easier and cleaner than WSGI and what , web.py ?
Finally the Heroku platform is * incomparable * .So yes , frameworks and platforms are a big part of the appeal of Ruby over Python these days.As for why Ruby might be doing better here ?
For one , Ruby is a more expressive than Python , and better designed than Perl ; it does have features other languages are missing .
For two , Ruby hit the scene after computers and the web were ubiquitous so it 's just good circumstance for something new , and perhaps better , to catch on .</tokentext>
<sentencetext>I Just took a Ruby job, after spending the last 5 years doing Python.Python is excellent because of it's maturity.
Ruby is excellent because of it's modernity.To use a metaphor, it's like the difference between dating a 35 year old career woman vs a 20 year old college girl.
The former is set in her ways and will offer a stable relationship with a lot of benefits.
The latter is full of potential and can teach you new tricks.In practical terms, Ruby happens to have a lot of programmers trying to change *how* software is written.
The 3rd party library and distribution eco-system (gems via gemcutter, rubyforge, github) is better than any other language.
Rack and Sinatra are easier and cleaner than WSGI and what, web.py?
Finally the Heroku platform is *incomparable*.So yes, frameworks and platforms are a big part of the appeal of Ruby over Python these days.As for why Ruby might be doing better here?
For one, Ruby is a more expressive than Python, and better designed than Perl; it does have features other languages are missing.
For two, Ruby hit the scene after computers and the web were ubiquitous so it's just good circumstance for something new, and perhaps better, to catch on.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30579148</id>
	<title>Ruby tag?</title>
	<author>Anonymous</author>
	<datestamp>1262021580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'm not too informed on how Shashdot's tagging system works so I could be making a silly complaint here, but isn't it a little dumb that this article isn't tagged "ruby"?  They're supposed to be tags to ease searching and categorization, not microcomments...</p></htmltext>
<tokenext>I 'm not too informed on how Shashdot 's tagging system works so I could be making a silly complaint here , but is n't it a little dumb that this article is n't tagged " ruby " ?
They 're supposed to be tags to ease searching and categorization , not microcomments.. .</tokentext>
<sentencetext>I'm not too informed on how Shashdot's tagging system works so I could be making a silly complaint here, but isn't it a little dumb that this article isn't tagged "ruby"?
They're supposed to be tags to ease searching and categorization, not microcomments...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574750</id>
	<title>Re:More importantly...</title>
	<author>Anonymous</author>
	<datestamp>1262033280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Compared to what?</p><p>C,C++, Or any lanauge that needs to be compiled to an optimized for the platform binary form to run, at the expense it only runs on type of platform.<br>Java, Dot Net, or any language that compiles to a byte code with is  optimized for its function and memory can be preallocated.<br>Python, Perl or other Scripting languages where there is little optimization that can go on as the code is running as it interprets the next line of code.</p><p>Speed isn't always what makes or break a language</p></htmltext>
<tokenext>Compared to what ? C,C + + , Or any lanauge that needs to be compiled to an optimized for the platform binary form to run , at the expense it only runs on type of platform.Java , Dot Net , or any language that compiles to a byte code with is optimized for its function and memory can be preallocated.Python , Perl or other Scripting languages where there is little optimization that can go on as the code is running as it interprets the next line of code.Speed is n't always what makes or break a language</tokentext>
<sentencetext>Compared to what?C,C++, Or any lanauge that needs to be compiled to an optimized for the platform binary form to run, at the expense it only runs on type of platform.Java, Dot Net, or any language that compiles to a byte code with is  optimized for its function and memory can be preallocated.Python, Perl or other Scripting languages where there is little optimization that can go on as the code is running as it interprets the next line of code.Speed isn't always what makes or break a language</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574520</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574540</id>
	<title>Before commenting, please complete this form</title>
	<author>Xunker</author>
	<datestamp>1262032080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Before commenting, please complete this form:</p><p>Sec. 1 Ruby v Python</p><p>[ ] I am a Ruby/Python fanboy/fangirl<br>[ ] I already have a positive/negative entrenched opinion of Python or Ruby<br>[ ] I cannot tell the difference between the two languages</p><p>Sec. 2 Ruby on Rails</p><p>[ ] I assume Ruby == Ruby on Rails</p><p>Sec. 3 Other</p><p>[ ] I program in PHP for it's robust design, consistent syntax and architectural soundness<br>[ ] I do not understand sarcasm</p><p>Scoring: If you answered any of the above questions in the affirmative, your comments may be dismissed out of hand.</p></htmltext>
<tokenext>Before commenting , please complete this form : Sec .
1 Ruby v Python [ ] I am a Ruby/Python fanboy/fangirl [ ] I already have a positive/negative entrenched opinion of Python or Ruby [ ] I can not tell the difference between the two languagesSec .
2 Ruby on Rails [ ] I assume Ruby = = Ruby on RailsSec .
3 Other [ ] I program in PHP for it 's robust design , consistent syntax and architectural soundness [ ] I do not understand sarcasmScoring : If you answered any of the above questions in the affirmative , your comments may be dismissed out of hand .</tokentext>
<sentencetext>Before commenting, please complete this form:Sec.
1 Ruby v Python[ ] I am a Ruby/Python fanboy/fangirl[ ] I already have a positive/negative entrenched opinion of Python or Ruby[ ] I cannot tell the difference between the two languagesSec.
2 Ruby on Rails[ ] I assume Ruby == Ruby on RailsSec.
3 Other[ ] I program in PHP for it's robust design, consistent syntax and architectural soundness[ ] I do not understand sarcasmScoring: If you answered any of the above questions in the affirmative, your comments may be dismissed out of hand.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30671598
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576112
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574020
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30670786
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574540
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30585336
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574848
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574164
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574048
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30590134
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30582354
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30580052
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30580556
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574338
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574542
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30573986
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30577142
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30578144
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574750
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574520
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30575080
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574638
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574520
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30670820
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_12_28_1424255_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30584540
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30575388
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574834
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574164
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574048
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574520
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574638
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30575080
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574750
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30578144
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574338
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30580556
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576544
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30580052
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30582354
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30585336
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30590134
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30671598
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30577142
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30670820
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574692
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574048
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574164
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574834
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30575388
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30584540
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574848
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30573986
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574542
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576120
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574540
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30670786
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574020
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30576112
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574880
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_12_28_1424255.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_12_28_1424255.30574252
</commentlist>
</conversation>
