From: Lothar Scholz Date: 2005-06-13T14:36:02+09:00 Subject: Re: python/ruby benchmark(don't shoot the messenger) Hello Michael, MC> On 6/12/05, Alexandru Popescu wrote: >> Also, I agree with the fact the optimization comes later in the >> dev cycles. But we need to have the >> doors open to optimize. Moreover, I read that in Ruby you can >> always go and code the hot spots in C. >> What if you don't have these resources? Which are the costs to >> bring such a resource and make him >> productive? MC> How does this issue relate to *ruby*? The same charge could be levied MC> at python, even J2EE. "What happens if you don't have the resources MC> to speed up something slow?" If a language is a few times faster then the risk factor that this happens is just lower. This is a management descision. There are many things to keep in balance when you start a project. Development time is just one of them and often not that important. I can just speak for the application domain where i worked for years: This is products for the mass market. Here you don't have something like "your customer". In this market you must look a lot about "your competitor" and this makes it different. Spending a few month more on development is just okay if the (peak !!) speed is well and competitive. This is a domain where Ruby is unfortunately not useable at the moment (missing a good GUI toolkit is the second reason). And i would like to see it possible to use it there too. -- Best regards, emailto: scholz at scriptolutions dot com Lothar Scholz http://www.ruby-ide.com CTO Scriptolutions Ruby, PHP, Python IDE 's