Actually, part of my reason for learning Ruby is because I have a project coming up that I will be designing, and i'm not sure if PHP is up to the task. I have been looking at ColdFusion, or more likely, the J2EE framework.
I prefer the philosophy and community of Ruby, but am still not sure at which point it is required. When would you say, ok, here is a job for Ruby?
I like Ruby because I find it easier to maintain than PHP or Perl.
A basic site requiring a MySQL backend for a few queries here and there is obviously a job for PHP, so at what stage is Ruby required?
I think 43 things is the largest RoR site by traffic, and this week we did 3,109,986 requests, averaging 444284 requests per day. (Requests through Rails. Hits for the site has been hovering just under the 2 million mark per day, the remaining 3/4 being images and so-forth.)
This is with 2 dual-xeon web servers and a dual-xeon DB server. We have very complex pages, and we're just past half our processor capacity on the web servers (I think, its hard to judge). The DB server has lots of room for growth.
To get back to the maintainable part...
We launched the site in 4 months with 5 developers, 4 of them had zero Ruby experience. About 6 months later we launched a new site. We're about to start working on a 3rd with an even shorter cycle. We didn't work on the new site for all of those 6 months, maybe 2 of them, and we borrowed (and overlayed) much of the code for the new site from the old.
We didn't plan to extend the original 43 things into 43 places, but Ruby let it happen without much difficulty.
···
On 16 Jul 2005, at 09:50, Tristan Knowles wrote:
--
Eric Hodel - drbrain@segment7.net - http://segment7.net
FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04
