What Lies Behind Rails
Ruby on Rails is fairly new. It was developed in 2004 by David Heinemeier Hansson as a byproduct to Basecamp. The reason that pushed Hansson to develop Rails was that Basecamp, even though it ran on Ruby, was not potent or flexible enough because they used PHP and Java. During that time, they did not count with the system that is accessible today. In order to make the development simpler, Hansson made his own framework, which he happened to base off simple ideas he had already tried out some other place.
Hansson based Rails on a pattern that breaks the application into three different parts. This pattern follows a Model / View / Controller sample. As you may already know, the models are your business objects describing the structure of a specific trouble, which your application is trying to resolve. The models are typically backed by a framework that carries the objects on to the database.
Then, the views are the patterns that provide data to the developer or user and the entire logic, which happens to be immediate in the different facets of the application. And the controller is the focal point of the whole system. It receives and deals with the different clients’ requests, as well as starting any needed changes in the models and generating the interpretation of the patterns.
Rails is famous for almost thinking on its own. This means that it doesn’t work to please everyone but rather on doing things the best way it knows how to. You may try to go against it and do things your own way, but you will definitely be better off just following what Rails says. This is a strong reason why Rails has been successful since its release.
When Hansson was developing Rails, he had programmer productivity in mind instead of performance. This generated many complaints and the truth is that many people were not happy.
One of the main complaints from users is that Rails doesn’t scale. However, even though it happens to be slower than PHP, programmers have been able to prove otherwise. Many have faith that Rails will only start to get stronger and a lot faster. In comparison to other languages,
Ruby is far from being slow; other implementations have been able to support this. Despite the negative talk that has been spreading around, Ruby will end up outdoing other frameworks.