Rails%203%20In%20Action

Reason #3: RubyGems
always, so we are nice,” often abbreviated to MINASWAN. People in the Ruby and Rails
communities are incredibly nice to everyone.
Another example of the excellent community around Ruby on Rails is the number
of conferences and gatherings held worldwide. The smallest of them are the intimate
hack sessions where people work together on applications and share ideas in a room.
Slightly bigger and more organized than that are the events such as Railscamps
(http://railscamps.org) which have about 150 people attend and run from Friday–
Monday, with interesting talks given on the Saturdays and Sundays. The largest however
is Railsconf, which has about 2,000 people in attendance.
There are hundreds of thousands, if not millions of people using Ruby on Rails
today, building great web applications with it and building the best web framework
community on the planet.
A.2 Reason #2: the speed and ease of development
The speed of how quickly you are able to develop a Ruby on Rails application is definitely
one of the main reasons that people gravitate toward (and stick with) the framework.
One documented case of this is that of a team that had developed an application
using a Java-based framework, which took four months. When that application
became difficult to maintain, alternative languages and frameworks were sought, with
Ruby and Ruby on Rails found to fit the bill adequately. The team re-implemented all
the features of the original Java-based application within three weeks, with less code
and more beautiful code.
Ruby on Rails follows a paradigm known as convention over configuration. This paradigm
is adopted not only by Rails, but also by other modern web frameworks. Rails is
designed in such a way that it takes care of the normal configuration that you may
have to do with other frameworks, leaving it up to you to get down to coding real features
for your application.
One example of this convention over configuration is the mapping between classes
designed to interact with the database and the tables related to these classes. If the
class is called Project then it can be assumed by Rails (and the people coding the
application) that the related table is going to be called projects. But this can be configured
using a setting in the class if that table name is not desired.
A.3 Reason #3: RubyGems
This third point is more about a general boon to the community of Ruby, but it plays a
key role in developing Rails applications.
As we stated before, the culture of the Rails community is one of self-improvement.
There are people who are consistently thinking of new ways to make other people’s
lives better. One of these ways is the RubyGems system, which allows people to share
libraries in a common format. By installing a gem, a user is able to use its code along
543