<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Two Minutes of Ruby</title>
	<atom:link href="http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/</link>
	<description></description>
	<lastBuildDate>Tue, 22 May 2012 10:36:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ben Griswold</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221388</link>
		<dc:creator>Ben Griswold</dc:creator>
		<pubDate>Fri, 23 Jul 2010 17:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221388</guid>
		<description>@Jeremy, You&#039;re right, Twitter is still Rails on the front-end with  Scala working behind the scenes. Here&#039;s a &lt;a href=&quot;http://www.artima.com/scalazine/articles/twitter_on_scala.html&quot; rel=&quot;nofollow&quot;&gt;pretty good write up&lt;/a&gt; for those interested.

@All Kind of to everyone&#039;s point, Ruby (not to be confused with Ruby on Rails) was causing problems for Twitter. As Robey Pointer from Twitter explains in the prior reference: 

&lt;blockquote cite=&quot;&quot;&gt;
We had a Ruby-based queueing system that we used for communicating between the Rails front ends and the daemons, and we ended up replacing that with one written in Scala. The Ruby one actually worked pretty decently in a normal steady state, but the startup time and the crash behavior were undesirable. It was a little too slow and memory intensive. Sometimes our peak loads would knock it out. And when it got knocked out, it was very slow to recover, which is not what we wanted. We wanted something that could handle the edge cases and the high load, maybe not as easily as a regular load, but with relative ease.&lt;/blockquote&gt;

I could be wrong but I think you&#039;re all right! Ruby is slow for some things and just fine for others. It all depends on the problem domain, making right choices and accepting trade-offs when they unfortunately come up.  

I guess...</description>
		<content:encoded><![CDATA[<p>@Jeremy, You&#8217;re right, Twitter is still Rails on the front-end with  Scala working behind the scenes. Here&#8217;s a <a href="http://www.artima.com/scalazine/articles/twitter_on_scala.html" rel="nofollow">pretty good write up</a> for those interested.</p>
<p>@All Kind of to everyone&#8217;s point, Ruby (not to be confused with Ruby on Rails) was causing problems for Twitter. As Robey Pointer from Twitter explains in the prior reference: </p>
<blockquote cite=""><p>
We had a Ruby-based queueing system that we used for communicating between the Rails front ends and the daemons, and we ended up replacing that with one written in Scala. The Ruby one actually worked pretty decently in a normal steady state, but the startup time and the crash behavior were undesirable. It was a little too slow and memory intensive. Sometimes our peak loads would knock it out. And when it got knocked out, it was very slow to recover, which is not what we wanted. We wanted something that could handle the edge cases and the high load, maybe not as easily as a regular load, but with relative ease.</p></blockquote>
<p>I could be wrong but I think you&#8217;re all right! Ruby is slow for some things and just fine for others. It all depends on the problem domain, making right choices and accepting trade-offs when they unfortunately come up.  </p>
<p>I guess&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Anderson</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221387</link>
		<dc:creator>Jeremy Anderson</dc:creator>
		<pubDate>Fri, 23 Jul 2010 16:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221387</guid>
		<description>@John Bristow: Doesn&#039;t Twitter still use Rails for the front-end and use Scala for their queuing? and @ Zach Curtis, I think that invalidates your argument about Ruby being slow compared to other languages. Scala can&#039;t handle the massive queue that twitter deals with. Has anyone here actually been responsible for scaling an application that handles as much real-time data as twitter? Be honest with yourself about the answer, they have a monumental task.</description>
		<content:encoded><![CDATA[<p>@John Bristow: Doesn&#8217;t Twitter still use Rails for the front-end and use Scala for their queuing? and @ Zach Curtis, I think that invalidates your argument about Ruby being slow compared to other languages. Scala can&#8217;t handle the massive queue that twitter deals with. Has anyone here actually been responsible for scaling an application that handles as much real-time data as twitter? Be honest with yourself about the answer, they have a monumental task.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Griswold</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221288</link>
		<dc:creator>Ben Griswold</dc:creator>
		<pubDate>Mon, 19 Jul 2010 14:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221288</guid>
		<description>@Kalpesh, I read &lt;a href=&quot;http://mislav.uniqpath.com/poignant-guide/&quot; rel=&quot;nofollow&quot;&gt;Why’s (Poignant) Guide to Ruby&lt;/a&gt; a few months back and now I&#039;m reading through a number of online tutorials (here&#039;s &lt;a href=&quot;http://rubylearning.com/satishtalim/tutorial.html&quot; rel=&quot;nofollow&quot;&gt;a pretty good one of many&lt;/a&gt;) and I&#039;m counting on Google to help me discover the syntax I need to solve the Euler problems. There&#039;s so much information online, I haven&#039;t purchased any books yet. Thanks for the question. I think I might publish a list of resources in an up coming post.</description>
		<content:encoded><![CDATA[<p>@Kalpesh, I read <a href="http://mislav.uniqpath.com/poignant-guide/" rel="nofollow">Why’s (Poignant) Guide to Ruby</a> a few months back and now I&#8217;m reading through a number of online tutorials (here&#8217;s <a href="http://rubylearning.com/satishtalim/tutorial.html" rel="nofollow">a pretty good one of many</a>) and I&#8217;m counting on Google to help me discover the syntax I need to solve the Euler problems. There&#8217;s so much information online, I haven&#8217;t purchased any books yet. Thanks for the question. I think I might publish a list of resources in an up coming post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kalpesh</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221282</link>
		<dc:creator>Kalpesh</dc:creator>
		<pubDate>Mon, 19 Jul 2010 06:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221282</guid>
		<description>How are you learning Ruby? 
Can you recommend any book/tutorial that you are using?</description>
		<content:encoded><![CDATA[<p>How are you learning Ruby?<br />
Can you recommend any book/tutorial that you are using?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Griswold</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221247</link>
		<dc:creator>Ben Griswold</dc:creator>
		<pubDate>Sat, 17 Jul 2010 17:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221247</guid>
		<description>Good comments, @Synapse. I have found that ReSharper actually helps me keep everything in order thanks to namespacing hints, the ability to refactor classes into their own files, etc. I&#039;m pretty good at organizing my code anyway though so ReSharper is more of an aid than a crutch for me in this regard.  I get your point though.  Thanks again.</description>
		<content:encoded><![CDATA[<p>Good comments, @Synapse. I have found that ReSharper actually helps me keep everything in order thanks to namespacing hints, the ability to refactor classes into their own files, etc. I&#8217;m pretty good at organizing my code anyway though so ReSharper is more of an aid than a crutch for me in this regard.  I get your point though.  Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: synapse</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221224</link>
		<dc:creator>synapse</dc:creator>
		<pubDate>Sat, 17 Jul 2010 05:35:32 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221224</guid>
		<description>@Zach
Speed of front-end is just a none-issue, cause you hit the DB first and cause you can always scale horizontally, get more boxes and you&#039;ll be ok. Facebook uses all kinds of technologies in the back-end like Erlang, C, whaterever, but they&#039;ve used PHP for front-end until recently.

Intellisense is really evil, cause it promotes creation of functions with tons of arguments and doesn&#039;t let you code top-to-bottom aka &quot;test first&quot;. Always gets in the way with its stupid suggestions for the methods I haven&#039;t implemented yet.

@Ben
Resharper is kinda evil cause with its excellent navigation no one cares to keep their assemblies/namespaces in order. Though it let&#039;s you clean the mess in no time.</description>
		<content:encoded><![CDATA[<p>@Zach<br />
Speed of front-end is just a none-issue, cause you hit the DB first and cause you can always scale horizontally, get more boxes and you&#8217;ll be ok. Facebook uses all kinds of technologies in the back-end like Erlang, C, whaterever, but they&#8217;ve used PHP for front-end until recently.</p>
<p>Intellisense is really evil, cause it promotes creation of functions with tons of arguments and doesn&#8217;t let you code top-to-bottom aka &#8220;test first&#8221;. Always gets in the way with its stupid suggestions for the methods I haven&#8217;t implemented yet.</p>
<p>@Ben<br />
Resharper is kinda evil cause with its excellent navigation no one cares to keep their assemblies/namespaces in order. Though it let&#8217;s you clean the mess in no time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Bristow</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221205</link>
		<dc:creator>Jon Bristow</dc:creator>
		<pubDate>Fri, 16 Jul 2010 15:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221205</guid>
		<description>@Zach: Twitter runs on scala now. Since early 2009.

As I&#039;ve been discussing with Ben, I think that getting an idea to market is your number 1 priority when creating an original web application idea.  If you can&#039;t get it out the door quickly, you&#039;re      likely to lose interest and momentum before you even see if the idea you had was a good one. Ruby lets you focus on your idea. After you are successful, you can worry about optimization/scalability/etc.

&quot;We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil&quot;</description>
		<content:encoded><![CDATA[<p>@Zach: Twitter runs on scala now. Since early 2009.</p>
<p>As I&#8217;ve been discussing with Ben, I think that getting an idea to market is your number 1 priority when creating an original web application idea.  If you can&#8217;t get it out the door quickly, you&#8217;re      likely to lose interest and momentum before you even see if the idea you had was a good one. Ruby lets you focus on your idea. After you are successful, you can worry about optimization/scalability/etc.</p>
<p>&#8220;We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Griswold</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221182</link>
		<dc:creator>Ben Griswold</dc:creator>
		<pubDate>Thu, 15 Jul 2010 20:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221182</guid>
		<description>@Zach - Thanks for the comments. Intellisense and even the compiler, for that matter, should be appreciated and used. Heck, I publicly shared that I learned much of the core Linq syntax by playing with the various ReSharper refactorings. All are valuable learning tools and code validators, for lack of a better term. That said, the Ruby community has embraced TDD, BDD, etc in order to reduce most of those risks. TDD/BDD come with some upfront cost but there is continuous return on that investment. The compiler and intellisense offers none. Well, there&#039;s still the learning aspect which intellisense provides but if a language is truly grokkable, maybe the learning aid is not really needed after all. And who knows? Maybe intellisense and ReSharper aren&#039;t really teaching us anything. Maybe they are just helping us fill in the blanks until we turn to them for that same task again and again? Don&#039;t get me wrong: I am forever thankful for VS and the tools which compliment static languages like C#, but maybe that&#039;s because it&#039;s all I really know? I&#039;m kind of thinking on paper here. You know. Hands frantically waving... Fists slamming...</description>
		<content:encoded><![CDATA[<p>@Zach &#8211; Thanks for the comments. Intellisense and even the compiler, for that matter, should be appreciated and used. Heck, I publicly shared that I learned much of the core Linq syntax by playing with the various ReSharper refactorings. All are valuable learning tools and code validators, for lack of a better term. That said, the Ruby community has embraced TDD, BDD, etc in order to reduce most of those risks. TDD/BDD come with some upfront cost but there is continuous return on that investment. The compiler and intellisense offers none. Well, there&#8217;s still the learning aspect which intellisense provides but if a language is truly grokkable, maybe the learning aid is not really needed after all. And who knows? Maybe intellisense and ReSharper aren&#8217;t really teaching us anything. Maybe they are just helping us fill in the blanks until we turn to them for that same task again and again? Don&#8217;t get me wrong: I am forever thankful for VS and the tools which compliment static languages like C#, but maybe that&#8217;s because it&#8217;s all I really know? I&#8217;m kind of thinking on paper here. You know. Hands frantically waving&#8230; Fists slamming&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Curtis</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221181</link>
		<dc:creator>Zach Curtis</dc:creator>
		<pubDate>Thu, 15 Jul 2010 19:58:07 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221181</guid>
		<description>Let me qualify the &quot;super slow&quot; comment with &quot;super slow compared to other languages (C#, Java, Etc).  Just saying super slow is a relative and ignorant comment.  Lol.</description>
		<content:encoded><![CDATA[<p>Let me qualify the &#8220;super slow&#8221; comment with &#8220;super slow compared to other languages (C#, Java, Etc).  Just saying super slow is a relative and ignorant comment.  Lol.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Curtis</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221180</link>
		<dc:creator>Zach Curtis</dc:creator>
		<pubDate>Thu, 15 Jul 2010 19:54:48 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221180</guid>
		<description>I have played with Ruby a touch and am becoming increasingly interested in it. Coming from php, I had a hard time adjusting to ASP.Net and all the costs associated.  It pays the bills as you said.  My only grumble with Ruby is the speed.  I know it is getting better but speed tests show time and time again how Ruby is super slow.  Look at Twitter! It is one of the slowest and highest failure rate services I have ever seen.  
I also disagree with the &quot;Intellisense is for chumps&quot; comment. Intellisense can help a person understand all the options available at a given point in code and therefore can help us understand what it does, even the obscure pieces.  It can be a crutch, but my favorite thing is that when I select something, I KNOW it is typed correctly and it is what I intended.  Being a JS lover I do not have the solid and extensive intellisense and that is fine, but I find mis-spellings and wrong casing all the time.  This requires at least as many refreshes as otherwise.  
Great post though.  I appreciate the opinion and look forward to working with Ruby more.</description>
		<content:encoded><![CDATA[<p>I have played with Ruby a touch and am becoming increasingly interested in it. Coming from php, I had a hard time adjusting to ASP.Net and all the costs associated.  It pays the bills as you said.  My only grumble with Ruby is the speed.  I know it is getting better but speed tests show time and time again how Ruby is super slow.  Look at Twitter! It is one of the slowest and highest failure rate services I have ever seen.<br />
I also disagree with the &#8220;Intellisense is for chumps&#8221; comment. Intellisense can help a person understand all the options available at a given point in code and therefore can help us understand what it does, even the obscure pieces.  It can be a crutch, but my favorite thing is that when I select something, I KNOW it is typed correctly and it is what I intended.  Being a JS lover I do not have the solid and extensive intellisense and that is fine, but I find mis-spellings and wrong casing all the time.  This requires at least as many refreshes as otherwise.<br />
Great post though.  I appreciate the opinion and look forward to working with Ruby more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Griswold</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221177</link>
		<dc:creator>Ben Griswold</dc:creator>
		<pubDate>Thu, 15 Jul 2010 19:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221177</guid>
		<description>@Dustin - I don&#039;t think I have the experienced to answer your question either. Maybe (hopefully) someone else will chime in. That said, I don&#039;t think I&#039;d be going too far out on a limb if I said that most Ruby hype is centered around Rails. And though you are learning Ruby as a means to learn Rails, I wouldn&#039;t be surprised if you start digging the language enough that you turn to it for web development, random scripts over possibly other applications development in the future. I have the sense that Ruby is a tool best suited for Rails and scripting, but I&#039;m sure it could lend itself elsewhere. For example, I&#039;ve heard about writing MVC views in dynamic languages like Ruby and I&#039;ve also read the benefits of using Ruby/Python for unit testing. Long answer to say, &quot;I&#039;m not sure. Sorry.&quot;</description>
		<content:encoded><![CDATA[<p>@Dustin &#8211; I don&#8217;t think I have the experienced to answer your question either. Maybe (hopefully) someone else will chime in. That said, I don&#8217;t think I&#8217;d be going too far out on a limb if I said that most Ruby hype is centered around Rails. And though you are learning Ruby as a means to learn Rails, I wouldn&#8217;t be surprised if you start digging the language enough that you turn to it for web development, random scripts over possibly other applications development in the future. I have the sense that Ruby is a tool best suited for Rails and scripting, but I&#8217;m sure it could lend itself elsewhere. For example, I&#8217;ve heard about writing MVC views in dynamic languages like Ruby and I&#8217;ve also read the benefits of using Ruby/Python for unit testing. Long answer to say, &#8220;I&#8217;m not sure. Sorry.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Griswold</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221176</link>
		<dc:creator>Ben Griswold</dc:creator>
		<pubDate>Thu, 15 Jul 2010 18:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221176</guid>
		<description>Note: I added some additional commentary on extending classes per Skyped comments Jon made about our lunch conversation.</description>
		<content:encoded><![CDATA[<p>Note: I added some additional commentary on extending classes per Skyped comments Jon made about our lunch conversation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin</title>
		<link>http://johnnycoder.com/blog/2010/07/15/two-minutes-of-ruby/comment-page-1/#comment-221175</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Thu, 15 Jul 2010 18:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://johnnycoder.com/blog/?p=1362#comment-221175</guid>
		<description>I just started learning Ruby so that I can learn Rails. I found that it is an interesting language but (and this is probably due to my lack of exp with Ruby) I can&#039;t see how you could make useful &quot;applications&quot; and not just scripts. Yes, you can do websites but so can PHP. Can you build enterprise apps?

That isn&#039;t a knock on Ruby, i&#039;m just asking a question.</description>
		<content:encoded><![CDATA[<p>I just started learning Ruby so that I can learn Rails. I found that it is an interesting language but (and this is probably due to my lack of exp with Ruby) I can&#8217;t see how you could make useful &#8220;applications&#8221; and not just scripts. Yes, you can do websites but so can PHP. Can you build enterprise apps?</p>
<p>That isn&#8217;t a knock on Ruby, i&#8217;m just asking a question.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

