I'm a big fan of both Ruby and Cocoa, though I have a lot more experience with Ruby. I agree that the users are sort of a mixed bag, but it seems most people are somewhere in the middle in terms of readability. Rails seems to really push for the latter though.
The "big idea" behind Rails is that you're not going to repeat yourself anywhere. I've played around with it and found it to be a really neat, fun development environment. You make the database, and then you just make a class with the name of the table, and it basically figures out the rest by talking to the database. The API is full of this kind of trick.
A couple weeks ago, I set up Typo, the Rails blog software, on one of my servers. I set up four deployments with FastCGi on Apache. Everything seemed to be working just fine, I gave out three of the logins to two other guys, and between the three of us, we managed to get the load average of the server up to 72 with four Rails apps loading up. I find this kind of astonishing.
So I would call it a pretty bulky framework, and I have zero confidence in FastCGI.
Since then I've been messing around with Drupal instead, which is more like a PHP web application framework. I strongly dislike PHP's syntax, but it's damn fast, and Rails (at least on Apache w/ FastCGI) is definitely not ready.
by Daniel Lyons — Jun 30
The "big idea" behind Rails is that you're not going to repeat yourself anywhere. I've played around with it and found it to be a really neat, fun development environment. You make the database, and then you just make a class with the name of the table, and it basically figures out the rest by talking to the database. The API is full of this kind of trick.
A couple weeks ago, I set up Typo, the Rails blog software, on one of my servers. I set up four deployments with FastCGi on Apache. Everything seemed to be working just fine, I gave out three of the logins to two other guys, and between the three of us, we managed to get the load average of the server up to 72 with four Rails apps loading up. I find this kind of astonishing.
So I would call it a pretty bulky framework, and I have zero confidence in FastCGI.
Since then I've been messing around with Drupal instead, which is more like a PHP web application framework. I strongly dislike PHP's syntax, but it's damn fast, and Rails (at least on Apache w/ FastCGI) is definitely not ready.