- Ruby on rails is: “a stack that contains components for most Web applications.”
Most. Heh. Wow, that’s really gonna suck when a team is fully invested/committed to Ruby on Rails and they come up with a need for something that’s not in the “stack”. Now, not only does the team need to figure out how to use the new/needed technology but they must also figure out how to integrate the technology into the Ruby on Rails stack. Fun! More work in a project with doesn’t have enough hours already.
- Ruby makes: “what most people do most of the time extremely easy”
- “37signals not only built their 5 world-class online applications purely with Ruby on Rails, but they support almost 400,000 users on just 13 servers.”
How vague is that? 400,000 what? Concurrent users with sessions? Doing what? Do you mean 400,000 enrolled users in the database? That’s a sad, “world-class” hardware hog (13 servers). Let me see here, the development is faster with Ruby on Rails (saving money) but they bought 10 more servers than the typical 400,000 enrolled user database needs.
When I put it all together in my head my summary is this: Ruby on Rails is like Ebonics for developers.
Ruby on Rails may be easier for development of most Web applications (a quoted 80% by David Heinemeier Hannson) but seriously, the same thing can be done with existing languages. Yes, Ruby on Rails/Ebonics has come to market faster than the other languages and because of that the other languages will be forced to get Web 2.0 savvy quickly. But Ruby on Rails has a lot of work to do on their “stack”. Take .NET for example, let’s say it takes Microsoft 2 years to Ebonicize so that you can do things like program AJAX quickly and easily. Once those Ebonics are in place you have access to a deep and extensive set of libraries that are baked. Ruby on Rails will building their “stack” for many years to come.