<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Clearing up some things about LinkedIn mobile&#8217;s move from Rails to node.js</title>
	<atom:link href="http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/feed/" rel="self" type="application/rss+xml" />
	<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/</link>
	<description>I say things!</description>
	<lastBuildDate>Sun, 28 Apr 2013 10:37:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jim Meyer</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-696</link>
		<dc:creator><![CDATA[Jim Meyer]]></dc:creator>
		<pubDate>Tue, 09 Oct 2012 09:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-696</guid>
		<description><![CDATA[Man, that was a lot of fun ... and a lot of learning. Nice post, Ikai.

And we didn&#039;t connect the iPhone app to PAL because &quot;the mobile platform&quot; was a better aggregation of data from multiple calls into a more flexible collection of objects which better served our purposes then. Some excellent work was done to make that happen by pretty much everyone in the group.

I still remember how fast we could provision and expand at Joyent. Made life much easier in our, er, less than resource efficient stack. We always knew there would come a time when it was more important to consolidate and drive to efficiency; at the time, we were optimized for shipping features and learning.

And regarding JRuby, the folks at http://eng.wealthfront.com/ got it, too. They&#039;re a smart bunch. I&#039;m glad to be with them, though I&#039;ll always miss LED.]]></description>
		<content:encoded><![CDATA[<p>Man, that was a lot of fun &#8230; and a lot of learning. Nice post, Ikai.</p>
<p>And we didn&#8217;t connect the iPhone app to PAL because &#8220;the mobile platform&#8221; was a better aggregation of data from multiple calls into a more flexible collection of objects which better served our purposes then. Some excellent work was done to make that happen by pretty much everyone in the group.</p>
<p>I still remember how fast we could provision and expand at Joyent. Made life much easier in our, er, less than resource efficient stack. We always knew there would come a time when it was more important to consolidate and drive to efficiency; at the time, we were optimized for shipping features and learning.</p>
<p>And regarding JRuby, the folks at <a href="http://eng.wealthfront.com/" rel="nofollow">http://eng.wealthfront.com/</a> got it, too. They&#8217;re a smart bunch. I&#8217;m glad to be with them, though I&#8217;ll always miss LED.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LinkedIn Moved From Rails To Node: 27 Servers Cut And Up To 20x Faster &#171; VietHiP</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-673</link>
		<dc:creator><![CDATA[LinkedIn Moved From Rails To Node: 27 Servers Cut And Up To 20x Faster &#171; VietHiP]]></dc:creator>
		<pubDate>Mon, 08 Oct 2012 14:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-673</guid>
		<description><![CDATA[[...] More background by Ikai Lan, who worked on the mobile server team at LinkedIn, says some facts were left out: the app made &#8220;a cross data center request, guys. Running on single-threaded Rails servers [...]]]></description>
		<content:encoded><![CDATA[<p>[...] More background by Ikai Lan, who worked on the mobile server team at LinkedIn, says some facts were left out: the app made &#8220;a cross data center request, guys. Running on single-threaded Rails servers [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Istvan (@lix)</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-661</link>
		<dc:creator><![CDATA[Istvan (@lix)]]></dc:creator>
		<pubDate>Mon, 08 Oct 2012 03:47:05 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-661</guid>
		<description><![CDATA[Cool story bro!

  I guess this situation with scalability, leads to the point where you have to ask, what is more important knowing my currently deployed stack and understand it or install a random solution and pick 3 metrics which the newer stack does better, and write an article about it. If the second one is cheaper (less engineering effort) do it; no question, this is a strategical decision.  However, this does not tell anything in terms of how good that platform is, or how good the new platform at all. I think using better solutions with Rails could have been less effort to fix your performance and scalability (without having numbers I can&#039;t be sure).

The other part is the &quot;what language is better&quot; argument, I guess the scientific comparison of these languages (Ruby and JS) could not find major differences, it just feels wrong to me to write javascript for a backend system when I know that I can express in Ruby the problem way better. I guess there are couple of other languages before I would even think about JS, but again, it is just personal preference. If there was a must situation I would probably use Coffee script, which more concise than JS.

Thanks for this writeup!]]></description>
		<content:encoded><![CDATA[<p>Cool story bro!</p>
<p>  I guess this situation with scalability, leads to the point where you have to ask, what is more important knowing my currently deployed stack and understand it or install a random solution and pick 3 metrics which the newer stack does better, and write an article about it. If the second one is cheaper (less engineering effort) do it; no question, this is a strategical decision.  However, this does not tell anything in terms of how good that platform is, or how good the new platform at all. I think using better solutions with Rails could have been less effort to fix your performance and scalability (without having numbers I can&#8217;t be sure).</p>
<p>The other part is the &#8220;what language is better&#8221; argument, I guess the scientific comparison of these languages (Ruby and JS) could not find major differences, it just feels wrong to me to write javascript for a backend system when I know that I can express in Ruby the problem way better. I guess there are couple of other languages before I would even think about JS, but again, it is just personal preference. If there was a must situation I would probably use Coffee script, which more concise than JS.</p>
<p>Thanks for this writeup!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Dunn</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-653</link>
		<dc:creator><![CDATA[James Dunn]]></dc:creator>
		<pubDate>Sun, 07 Oct 2012 13:08:53 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-653</guid>
		<description><![CDATA[Thank you for posting this. I had a feeling that there was more to the story than the node evangelists would have us believe. The rewrite factor being the most obvious. Any time you start a project with all of the requirements in mind, the result is going to be much better than when it grows organically.]]></description>
		<content:encoded><![CDATA[<p>Thank you for posting this. I had a feeling that there was more to the story than the node evangelists would have us believe. The rewrite factor being the most obvious. Any time you start a project with all of the requirements in mind, the result is going to be much better than when it grows organically.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Klabnik (@steveklabnik)</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-647</link>
		<dc:creator><![CDATA[Steve Klabnik (@steveklabnik)]]></dc:creator>
		<pubDate>Sat, 06 Oct 2012 23:13:25 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-647</guid>
		<description><![CDATA[&gt; MRI is generally slower than YARV (Ruby 1.9),

Just so you know, Ruby 1.9 is officially also MRI, it was only called YARV during development.]]></description>
		<content:encoded><![CDATA[<p>&gt; MRI is generally slower than YARV (Ruby 1.9),</p>
<p>Just so you know, Ruby 1.9 is officially also MRI, it was only called YARV during development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruby on Rails vs. Node.js &#124; bekinin.com</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-637</link>
		<dc:creator><![CDATA[Ruby on Rails vs. Node.js &#124; bekinin.com]]></dc:creator>
		<pubDate>Sat, 06 Oct 2012 07:30:38 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-637</guid>
		<description><![CDATA[[...] Node.js some time ago for performance and scalability reasons. A former LinkedIn team member reacted explaining what went wrong, in his [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Node.js some time ago for performance and scalability reasons. A former LinkedIn team member reacted explaining what went wrong, in his [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wangstabill</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-633</link>
		<dc:creator><![CDATA[wangstabill]]></dc:creator>
		<pubDate>Fri, 05 Oct 2012 18:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-633</guid>
		<description><![CDATA[Awesome post!  I work with both Rails and Node daily, and I use them for what they&#039;re good for.  I&#039;m curious: I hate Java, but could I see performance gains from running my Ruby programs in JRuby instead of YARV?]]></description>
		<content:encoded><![CDATA[<p>Awesome post!  I work with both Rails and Node daily, and I use them for what they&#8217;re good for.  I&#8217;m curious: I hate Java, but could I see performance gains from running my Ruby programs in JRuby instead of YARV?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ Rollins</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-628</link>
		<dc:creator><![CDATA[Russ Rollins]]></dc:creator>
		<pubDate>Fri, 05 Oct 2012 15:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-628</guid>
		<description><![CDATA[Appreciate your post, based on my experience with a heavily utilized Rails 1.2.3 app, my findings are quite similar (the one I&#039;m looking to port launched in 2007 and averages  &gt; 1m req/month).]]></description>
		<content:encoded><![CDATA[<p>Appreciate your post, based on my experience with a heavily utilized Rails 1.2.3 app, my findings are quite similar (the one I&#8217;m looking to port launched in 2007 and averages  &gt; 1m req/month).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paulatcyberstride</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-625</link>
		<dc:creator><![CDATA[paulatcyberstride]]></dc:creator>
		<pubDate>Fri, 05 Oct 2012 13:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-625</guid>
		<description><![CDATA[Really great article.   Your frankness on how IT decisions get made is refreshing for those of us who&#039;ve been living that, and wondering why everyone else seems to think they&#039;re all 100% rational. :D

https://plus.google.com/102874503764972429803/posts/SZQR3eKYhWn]]></description>
		<content:encoded><![CDATA[<p>Really great article.   Your frankness on how IT decisions get made is refreshing for those of us who&#8217;ve been living that, and wondering why everyone else seems to think they&#8217;re all 100% rational. :D</p>
<p><a href="https://plus.google.com/102874503764972429803/posts/SZQR3eKYhWn" rel="nofollow">https://plus.google.com/102874503764972429803/posts/SZQR3eKYhWn</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnconroy (@johnconroy)</title>
		<link>http://ikaisays.com/2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/#comment-621</link>
		<dc:creator><![CDATA[johnconroy (@johnconroy)]]></dc:creator>
		<pubDate>Fri, 05 Oct 2012 08:10:35 +0000</pubDate>
		<guid isPermaLink="false">http://ikaisays.com/?p=232#comment-621</guid>
		<description><![CDATA[Thanks for this extremely informative article... the highscalability article&#039;s headline takeaways seemed way too strong to be the full story]]></description>
		<content:encoded><![CDATA[<p>Thanks for this extremely informative article&#8230; the highscalability article&#8217;s headline takeaways seemed way too strong to be the full story</p>
]]></content:encoded>
	</item>
</channel>
</rss>
