When to use Ruby on Rails ?

I have a general question under which circumstances and where to use Ruby on Rails .

Regards

ruby is a new framework which is a request and response based and this is used at server side programing

Originally posted by mahesha:
ruby is a new framework which is a request and response based and this is used at server side programing

Actually ruby is a language. Ruby on rails is what you mean.

"mahesha", you have previously been warned on multiple occasions regarding adjusting your display name to meet JavaRanch standards. This is not optional, and this is your final warning. Adjust your display name to comply with the required standards prior to your next post.

Failure to comply will result in the removal of your account.

bear
JavaRanch Sheriff

RoR can be used to rapidly develop new web application when compared to other frameworks. It uses conventions over any external configuration file.

Originally posted by Prad Dip:
It uses conventions over any external configuration file.

There are many newer frameworks that can boast this as well -- many based on Java. So this is not something that's unique to Rails.

Originally posted by jatandar dhirwani:
I have a general question under which circumstances and where to use Ruby on Rails .

Regards

If you need to write a web application that doesn't do anything out of the ordinary, RoR would be perfect. If it is going to use a lot of Ajax, you probably can't do better. Besides, Django, there really isn't a web framework that can touch RoR in the areas it excels.

Problems with RoR include deployment. It is a pain, to put it midly, although it is getting better, especially among rails hosts. I am not sure it scales as well as say Java can. Rails is about 4 years old and under constant change, so who knows. The constant change is annoying. Tutorials written 6 months ago, might not work at all without some tweaking. Especially scaffolding and pagination examples.

Originally posted by Bear Bibeault:

There are many newer frameworks that can boast this as well -- many based on Java. So this is not something that's unique to Rails.

Wasn't Rails the first framework to come up with it. Others followed it ?

Originally posted by Prad Dip:

Wasn't Rails the first framework to come up with it. Others followed it ?

I don't think that really matters. I seriously doubt convention over configuration didn't exist before Rails.

There may be Java based frameworks that have this philosophy, but since they are based on Java, they will not have the flexibility of Rails because of Ruby.