<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: 5 Reasons to Hate Ruby</title>
	<link>http://ramikayyali.com/archives/2007/04/18/rubyhate</link>
	<description>Unfocused, Opinionated.</description>
	<pubDate>Tue, 06 Jan 2009 04:54:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Tom</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20059</link>
		<author>Tom</author>
		<pubDate>Wed, 18 Apr 2007 03:27:30 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20059</guid>
					<description>&lt;p&gt;^_^&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>^_^</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Preston Lee</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20206</link>
		<author>Preston Lee</author>
		<pubDate>Thu, 19 Apr 2007 21:48:34 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20206</guid>
					<description>&lt;p&gt;It sounds like you're expecting Ruby to be just another scripting language. It's true that dynamically bound languages such as Ruby do take a certain amount of learning, but &lt;em&gt;all&lt;/em&gt; object-oriented languages require you to put in that effort.&lt;/p&gt;

&lt;p&gt;Of course Ruby has arrays and hashes, and they're even notated in the same manner as Perl: [] and {}, respectively. Read up a bit on some other object-oriented languages such as C++ or Java and I think you'll begin to see why the type of the referent is more important than than the exact type of the reference.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It sounds like you&#8217;re expecting Ruby to be just another scripting language. It&#8217;s true that dynamically bound languages such as Ruby do take a certain amount of learning, but <em>all</em> object-oriented languages require you to put in that effort.</p>
<p>Of course Ruby has arrays and hashes, and they&#8217;re even notated in the same manner as Perl: [] and {}, respectively. Read up a bit on some other object-oriented languages such as C++ or Java and I think you&#8217;ll begin to see why the type of the referent is more important than than the exact type of the reference.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Rami Kayyali</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20214</link>
		<author>Rami Kayyali</author>
		<pubDate>Thu, 19 Apr 2007 23:26:02 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20214</guid>
					<description>&lt;p&gt;Preston, I hope you didn't get me wrong. I fell in love with Ruby, and that dynamism is exactly what tipped the scales.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Preston, I hope you didn&#8217;t get me wrong. I fell in love with Ruby, and that dynamism is exactly what tipped the scales.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: anon</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20215</link>
		<author>anon</author>
		<pubDate>Thu, 19 Apr 2007 23:40:31 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20215</guid>
					<description>&lt;p&gt;Ruby does have $_, $0, $1, $2, $2 etc.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ruby does have $_, $0, $1, $2, $2 etc.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Lee Preston Nails</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20219</link>
		<author>Lee Preston Nails</author>
		<pubDate>Fri, 20 Apr 2007 01:11:30 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20219</guid>
					<description>&lt;p&gt;Preston,&lt;/p&gt;

&lt;p&gt;I think you may have read this with your humor/sarcasm module uninstalled...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Preston,</p>
<p>I think you may have read this with your humor/sarcasm module uninstalled&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Paul Battley</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20220</link>
		<author>Paul Battley</author>
		<pubDate>Fri, 20 Apr 2007 01:12:44 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20220</guid>
					<description>&lt;p&gt;Ruby may not be able to &lt;code&gt;&lt;strong&gt;use&lt;/strong&gt; English&lt;/code&gt;, but you can &lt;code&gt;&lt;strong&gt;require&lt;/strong&gt;&lt;/code&gt; it:&lt;/p&gt;

&lt;p&gt;&lt;a href="http://ruby-doc.org/stdlib/libdoc/English/rdoc/index.html" rel="nofollow"&gt;http://ruby-doc.org/stdlib/libdoc/English/rdoc/index.html&lt;/a&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ruby may not be able to <code><strong>use</strong> English</code>, but you can <code><strong>require</strong></code> it:</p>
<p><a href="http://ruby-doc.org/stdlib/libdoc/English/rdoc/index.html" rel="nofollow">http://ruby-doc.org/stdlib/libdoc/English/rdoc/index.html</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Rami Kayyali</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20223</link>
		<author>Rami Kayyali</author>
		<pubDate>Fri, 20 Apr 2007 01:51:42 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20223</guid>
					<description>&lt;p&gt;Hey look at that. Thanks for the tip Paul.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hey look at that. Thanks for the tip Paul.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Nicolás Sanguinetti</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20226</link>
		<author>Nicolás Sanguinetti</author>
		<pubDate>Fri, 20 Apr 2007 06:37:08 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20226</guid>
					<description>&lt;p&gt;ROFL&lt;/p&gt;

&lt;p&gt;&lt;/code&gt;puts "Just another ruby hacker"&lt;/code&gt;&lt;/pre&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>ROFL</p>
<p>puts &#8220;Just another ruby hacker&#8221;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Craig</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20230</link>
		<author>Craig</author>
		<pubDate>Fri, 20 Apr 2007 08:52:31 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20230</guid>
					<description>&lt;p&gt;The reason that there are so few keywords is becasue so much of that functionality is wrapped up as object methods and not as language wide functions.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The reason that there are so few keywords is becasue so much of that functionality is wrapped up as object methods and not as language wide functions.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ted</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20235</link>
		<author>Ted</author>
		<pubDate>Fri, 20 Apr 2007 10:32:41 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20235</guid>
					<description>&lt;p&gt;Class &lt;em&gt;is&lt;/em&gt; an object&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Class <em>is</em> an object</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Preston Lee</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20275</link>
		<author>Preston Lee</author>
		<pubDate>Fri, 20 Apr 2007 21:17:45 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20275</guid>
					<description>&lt;p&gt;I didn't grok the sarcasm.. sorry :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t grok the sarcasm.. sorry :)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Nolan</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20297</link>
		<author>Nolan</author>
		<pubDate>Sat, 21 Apr 2007 04:40:55 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20297</guid>
					<description>&lt;p&gt;What are you talking about in number 2, Ruby has a lot of klass&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What are you talking about in number 2, Ruby has a lot of klass</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ruby on Rails走向企业 : 透明思考</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20302</link>
		<author>Ruby on Rails走向企业 : 透明思考</author>
		<pubDate>Sat, 21 Apr 2007 06:54:48 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20302</guid>
					<description>&lt;p&gt;[...] 我的标题不是一个问句。因为我已经相当确定，Ruby on Rails走向企业是早晚的事情。已经有太多的讨论围绕着“用Rails要快多少多少倍”展开。但是，对于企业级超复杂来说，开发的效率只是一方面。至少还有其他几个方面是必须关注的。非功能性需求，也就是软件的-ilities：性能，并发吞吐量，伸缩性，安全，等等。完整的生命周期支持：需求，设计，开发，配置管理，质量保证，部署，维护，升级。软件生命周期的各个环节是否有适当的工具和/或最佳实践来覆盖。系统整合。与遗留系统是否能够协同工作。这主要体现在两个方面：（1）消息系统；（2）遗留数据库。 实际上动态语言早已在各种企业IT系统中扮演胶水的角色，一些成熟的组织早已认识到它们并不止是急就章拼凑软件的法宝。动态语言本身的特点使得它们能够相当漂亮地描述各种领域，这正是为何Rails只会在Ruby上出现的原因。至于前面提到的、企业级超复杂所看重的三个方面。结合Apache、Mongrel和HAProxy的部署方案已经被证明具有轻松超过任何J2EE应用服务器的性能和吞吐量，无共享架构使其具有完全线性的水平伸缩能力；至于安全性，Unix本身就已经构造了完备而可靠的安全体系。在今年的RailsConf上，我们将看到关于“如何部署高性能企业级Rails应用环境”的产品和最佳实践。在生命周期方面，我们已经有了CruiseControl.rb和Capistrano；我们即将看到Mingle的正式亮相，以及基于这些工具的最佳实践。系统整合或许是目前最不明朗的一个领域：我们有ActiveMessaging，我们有复合主键支持，但是很明显这离着“方便的遗留系统整合”还有相当距离。在未来的一年中，这可能是“企业级Rails”最有看头的一个领域。总而言之，不难看到，即便是对于企业级超复杂的要求，Ruby和Rails也已经做好了——至少是大部分的——准备。即便客气一点不说“Rails比J2EE还要适合企业使用”这样的话，对于那些愿意承担一定风险来提升IT效率的企业而言，是的，Ruby和Rails整装待发。 [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] 我的标题不是一个问句。因为我已经相当确定，Ruby on Rails走向企业是早晚的事情。已经有太多的讨论围绕着“用Rails要快多少多少倍”展开。但是，对于企业级超复杂来说，开发的效率只是一方面。至少还有其他几个方面是必须关注的。非功能性需求，也就是软件的-ilities：性能，并发吞吐量，伸缩性，安全，等等。完整的生命周期支持：需求，设计，开发，配置管理，质量保证，部署，维护，升级。软件生命周期的各个环节是否有适当的工具和/或最佳实践来覆盖。系统整合。与遗留系统是否能够协同工作。这主要体现在两个方面：（1）消息系统；（2）遗留数据库。 实际上动态语言早已在各种企业IT系统中扮演胶水的角色，一些成熟的组织早已认识到它们并不止是急就章拼凑软件的法宝。动态语言本身的特点使得它们能够相当漂亮地描述各种领域，这正是为何Rails只会在Ruby上出现的原因。至于前面提到的、企业级超复杂所看重的三个方面。结合Apache、Mongrel和HAProxy的部署方案已经被证明具有轻松超过任何J2EE应用服务器的性能和吞吐量，无共享架构使其具有完全线性的水平伸缩能力；至于安全性，Unix本身就已经构造了完备而可靠的安全体系。在今年的RailsConf上，我们将看到关于“如何部署高性能企业级Rails应用环境”的产品和最佳实践。在生命周期方面，我们已经有了CruiseControl.rb和Capistrano；我们即将看到Mingle的正式亮相，以及基于这些工具的最佳实践。系统整合或许是目前最不明朗的一个领域：我们有ActiveMessaging，我们有复合主键支持，但是很明显这离着“方便的遗留系统整合”还有相当距离。在未来的一年中，这可能是“企业级Rails”最有看头的一个领域。总而言之，不难看到，即便是对于企业级超复杂的要求，Ruby和Rails也已经做好了——至少是大部分的——准备。即便客气一点不说“Rails比J2EE还要适合企业使用”这样的话，对于那些愿意承担一定风险来提升IT效率的企业而言，是的，Ruby和Rails整装待发。 [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Darren Wang</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20313</link>
		<author>Darren Wang</author>
		<pubDate>Sat, 21 Apr 2007 10:10:35 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20313</guid>
					<description>&lt;p&gt;呵呵，或许吧&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>呵呵，或许吧</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Rami Kayyali</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20314</link>
		<author>Rami Kayyali</author>
		<pubDate>Sat, 21 Apr 2007 10:29:40 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20314</guid>
					<description>&lt;p&gt;I would love to understand what the above means. Anyone can translate?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I would love to understand what the above means. Anyone can translate?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: menneke</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20507</link>
		<author>menneke</author>
		<pubDate>Mon, 23 Apr 2007 13:40:55 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-20507</guid>
					<description>&lt;p&gt;Rami, here, I solved that for you... ;-)&lt;/p&gt;

&lt;p&gt;Our mark 标 题 non- right one 个 问 phrase. Cause 为 our 已 经 suitable 确 fixed, Ruby ON Rails travelling 企 业 right it is quick 晚 mark circumstance. The 已 经 possession thickly the multi marks 讨 论 围 绕 arrival “business Rails main point it is pleasant some some time” spreading/displaying 开. 但 right, 对 于 企 业 级 super 复 杂 it comes, 说, 开 发 mark 效 ratio merely right one side the surface. Reaching little 还 possession 其 other 几 个 direction right necessary 须 关 note. Non Isao talent characteristic demand seeking, 也 engaging in right 软 case - ilities: Efficiency, 并 发 吞 吐 quantity, Noboru 缩 characteristic, safety, and so on and so on. All-inclusive integral life periodic support: Demand seeking, 设 计, 开 发, management and 质 quantitative preservation of arrangement 证, post, 维 护, sho 级. The 软 case life periodic each 个 环 节 right no possession 适 this mark tool harmony/或 most 实 践 it comes good, 覆 盖. Type 统 adjustment. Giving 遗 stationary type 统 right no talent 够 协 the same construction. 这 Principal body 现 resident in 两 个 direction: (1) news system 统; (2) 遗 residue 据 库. 动 态 语 word on the 实 际 quickly 已 扮 performing 胶 water target angle color in the resident in each 种 企 业 IT 统, one 些 maturity 组 织 it is quick 已 认 识 arriving at 它 们 并 non- stopping right urgent engaging in chapter 拼 凑 软 case method treasure. Main body special point use profitable 它 们 talent of 动 态 语 word 够 the suitable drifting Akira area drawing predicative each 种 领 limits, 这 correct right 为 no Rails on meeting resident in Ruby it comes out merely, 现 mark cause. Reaching 于 front stopping arriving at, 企 业 级 super 复 杂 place watching it is heavy mark three 个 direction. 结 combination Apache, Mongrel harmony HAProxy post design 已 经 suffering 证 discernment possession 轻 pine super 过 duty no J2EE 应 business clothes 务 vessel efficiency harmony 吞 吐 quantity, also 无 享 rack 构 use 其 possession complete 线 sexual horizontal Noboru 缩 ability; Reaching 于 safety, main body engaging in 已 经 构 structure Ryo all-inclusive 备 而 yes of UNIX 靠 mark safe system. On resident in this year RailsConf, our 们 military officer watching arriving at 关 于 “how the post high performance 企 业 级 Rails 应 business 环 boundary” mark 产 item harmony most it is good 实 践. Resident in life periodic direction, our 们 已 经 possession Ryo CruiseControl.rb harmony Capistrano; Our 们 same military officer watching arriving at Mingle formal Akira phase, from here and the basic 于 这 些 tool most it is good 实 践. Type 统 adjustable 或 许 right immediate most preposterous one 个 领 limits: Our 们 possession ActiveMessaging, our 们 possession 复 combination main 键 support and 但 right 很 discernment 显 这 离 arrival “one flight mark 遗 stationary type 统 adjustable” 还 possession suitable spur 离. Resident in future throughout the year, 这 possible right “企 业 级 Rails” most possession watching 头 the mark one 个 领 limits. 总 而 word 之, non- 难 watching arriving at, same flight right 对 于 企 业 级 super 复 杂 mark request and Ruby harmony Rails 也 已 经 做 good Ryo - - reaching little right most - - associate 备. Same flight customer 气 point non- 说 “Rails ratio J2EE 还 main point 适 combination 企 业 use” 这 样 the mark 话, 对 于 那 些 愿 mind acceptance bearing uniformity 风 险 it comes, stopping sho IT 效 ratio 企 业 而 word, right, the Ruby harmony Rails integral equipment 待 发.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Rami, here, I solved that for you&#8230; ;-)</p>
<p>Our mark 标 题 non- right one 个 问 phrase. Cause 为 our 已 经 suitable 确 fixed, Ruby ON Rails travelling 企 业 right it is quick 晚 mark circumstance. The 已 经 possession thickly the multi marks 讨 论 围 绕 arrival “business Rails main point it is pleasant some some time” spreading/displaying 开. 但 right, 对 于 企 业 级 super 复 杂 it comes, 说, 开 发 mark 效 ratio merely right one side the surface. Reaching little 还 possession 其 other 几 个 direction right necessary 须 关 note. Non Isao talent characteristic demand seeking, 也 engaging in right 软 case - ilities: Efficiency, 并 发 吞 吐 quantity, Noboru 缩 characteristic, safety, and so on and so on. All-inclusive integral life periodic support: Demand seeking, 设 计, 开 发, management and 质 quantitative preservation of arrangement 证, post, 维 护, sho 级. The 软 case life periodic each 个 环 节 right no possession 适 this mark tool harmony/或 most 实 践 it comes good, 覆 盖. Type 统 adjustment. Giving 遗 stationary type 统 right no talent 够 协 the same construction. 这 Principal body 现 resident in 两 个 direction: (1) news system 统; (2) 遗 residue 据 库. 动 态 语 word on the 实 际 quickly 已 扮 performing 胶 water target angle color in the resident in each 种 企 业 IT 统, one 些 maturity 组 织 it is quick 已 认 识 arriving at 它 们 并 non- stopping right urgent engaging in chapter 拼 凑 软 case method treasure. Main body special point use profitable 它 们 talent of 动 态 语 word 够 the suitable drifting Akira area drawing predicative each 种 领 limits, 这 correct right 为 no Rails on meeting resident in Ruby it comes out merely, 现 mark cause. Reaching 于 front stopping arriving at, 企 业 级 super 复 杂 place watching it is heavy mark three 个 direction. 结 combination Apache, Mongrel harmony HAProxy post design 已 经 suffering 证 discernment possession 轻 pine super 过 duty no J2EE 应 business clothes 务 vessel efficiency harmony 吞 吐 quantity, also 无 享 rack 构 use 其 possession complete 线 sexual horizontal Noboru 缩 ability; Reaching 于 safety, main body engaging in 已 经 构 structure Ryo all-inclusive 备 而 yes of UNIX 靠 mark safe system. On resident in this year RailsConf, our 们 military officer watching arriving at 关 于 “how the post high performance 企 业 级 Rails 应 business 环 boundary” mark 产 item harmony most it is good 实 践. Resident in life periodic direction, our 们 已 经 possession Ryo CruiseControl.rb harmony Capistrano; Our 们 same military officer watching arriving at Mingle formal Akira phase, from here and the basic 于 这 些 tool most it is good 实 践. Type 统 adjustable 或 许 right immediate most preposterous one 个 领 limits: Our 们 possession ActiveMessaging, our 们 possession 复 combination main 键 support and 但 right 很 discernment 显 这 离 arrival “one flight mark 遗 stationary type 统 adjustable” 还 possession suitable spur 离. Resident in future throughout the year, 这 possible right “企 业 级 Rails” most possession watching 头 the mark one 个 领 limits. 总 而 word 之, non- 难 watching arriving at, same flight right 对 于 企 业 级 super 复 杂 mark request and Ruby harmony Rails 也 已 经 做 good Ryo - - reaching little right most - - associate 备. Same flight customer 气 point non- 说 “Rails ratio J2EE 还 main point 适 combination 企 业 use” 这 样 the mark 话, 对 于 那 些 愿 mind acceptance bearing uniformity 风 险 it comes, stopping sho IT 效 ratio 企 业 而 word, right, the Ruby harmony Rails integral equipment 待 发.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: gigix</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-22731</link>
		<author>gigix</author>
		<pubDate>Sat, 12 May 2007 17:48:16 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-22731</guid>
					<description>&lt;p&gt;Sorry Rami...that's a trackback from my blog. Following is what I said in that blog entry:&lt;/p&gt;

&lt;p&gt;To be used in "enterprises", Ruby has following (major) chanllenges:&lt;/p&gt;

&lt;p&gt;(1) performance/scalability/maintainability...of deployment
(2) support for overall lifecycle: test, continuous integration, deployment, etc.
(3) integration with legacy: messaging, legacy databases, etc.&lt;/p&gt;

&lt;p&gt;Fortunately, there are (at least, potential) solutions for all of these challenges. For enterprises willing to take (a little bit) higher risk, Ruby/Rails is already usable.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sorry Rami&#8230;that&#8217;s a trackback from my blog. Following is what I said in that blog entry:</p>
<p>To be used in &#8220;enterprises&#8221;, Ruby has following (major) chanllenges:</p>
<p>(1) performance/scalability/maintainability&#8230;of deployment<br />
(2) support for overall lifecycle: test, continuous integration, deployment, etc.<br />
(3) integration with legacy: messaging, legacy databases, etc.</p>
<p>Fortunately, there are (at least, potential) solutions for all of these challenges. For enterprises willing to take (a little bit) higher risk, Ruby/Rails is already usable.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Rami Kayyali</title>
		<link>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-22734</link>
		<author>Rami Kayyali</author>
		<pubDate>Sat, 12 May 2007 17:57:39 +0000</pubDate>
		<guid>http://ramikayyali.com/archives/2007/04/18/rubyhate#comment-22734</guid>
					<description>&lt;p&gt;Thanks Gigix, I was starting to get worried. Seems that not everyone likes sarcasm.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks Gigix, I was starting to get worried. Seems that not everyone likes sarcasm.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
