Is Ruby on Rails good for large scale projects?

I am working on a presentation about RoR. It's looking good except I cannot really find anything for a "Problems" section. There seems to be none. :)

Particularly I am interested in:

1. What issues are there with maintainability/management when 开发者_运维知识库multiple developers are involved in large-scale RoR project?
2. What specific considerations are there for developers on such large-scale projects using dynamically typed languages versus statically typed languages?
3. Why might RoR not be suitable for large-scale projects?

I could not find anything on this googling the Internet. I would like to hear your thoughts about these points?

Thank you, Arkadiy

I'm certain you can find a lot of this on the 'net, but I'm happy to oblige.

1. Maintainability: Ruby and Rails are all about creating more maintainable code at the expense of a little performance. That's why Ruby is a dynamic language in the first place. As far as developers/teams are concerned, Rails is great for creating and maintaining code that is easy to understand and maintain.
2. Dynamic vs Static: From the perspective of a development team, static languages have a the unique advantage of being very explicit. There isn't magic to confuse new developers, and there should be little work in terms of chasing down ghosts (in theory, anyways). That advantage is quickly outweighed by the ability of a dynamic language to really take advantage of OOP and get started developing quickly.
3. Suitability: I can't think of any good reasons. It's test-driven, proven, and extremely well designed. It was made to do the job, so it doesn't surprise me that this is the case. :)

Most RoR developer team works on MAC in my experience. Using git or svn for version control. Most use TextMate or Komodo. Special with Komodo Pro you can use it well in teams. A good svn client there is Versions

I didn't worked in bigger teams then 5 developers, that isn't large scale I think :) But the framework itself is much easier to handle like most other I have seen. Mostly used in Scrum-Teams but if yo have a good organisation I don't see any disadvantage using RoR in large teams.

The code documentation tools are handy, splitting the models, controllers and views up in different sections for team members shouldn't be a big deal and setting up test servers with nightly builts is very easy.

We use RoR in linux and windows environments and have very good productive experience made with it. Technical it is as scaleable as other large frameworks, with sql_sessions and mem_cache you can setup easy a server farm to run it for thousands or millions of users.

So imho: It is capable for any size of team.

For scalability, if twitter can doit so i think you can do it too.

And Maintainability, like in any other programming language, you need use some kind of versions control, svn or git.