Ruby in large project.

Today I had the first experience with Ruby in the large project with 10 developers.
I was very impressed by code, because it's very messy. Yes, Ruby is very laconic. Yes, It's easier to write on ruby then Java or C#. BUT: It's very difficult to support large projects, because the is no strict layer separation (Why this code "<%=User.find(session[:id]).name%>" can't been written in view?), something like ASP.NET's code-behind practice, Java's and .NET's Data Layer.

Of course, it possible to write the understable code using it, but it's not easy to do in outsourcing environment, especially if the project is written by few geo-distributed teams.

I am sure the the most important part of ruby project is Agile development. So the first milestone of every Ruby project is "Apply Agile development practice in the team".

The second ruby "benefit" example:
Currently, the company where I am working, provides the testing services for Polish outsourcing company on the ERP system development.
This project is been writing using Ruby on rails framework. Only Ruby experts work on it. It has been developed very fast. But it contains a lot of bugs.

I have already started a development of small eCommerce site using Ruby and i am sure that it's a good choice. But i am not sure about the large projects.