Why Ruby-on-Rails?

[jkobylt]

Hello everybody,

I've been reading a lot about Ruby-on-Rails, and I must say, I'm still not sure why it's so great. What is it better than? Java? C++? I read the documentation in the official http://www.rubyonrails.com website, and I understand it's a simple language code web applications with. But how much better is it really?

From my understanding, the language is simpler and less specific than Java. But Java is quick and efficient because all variables are specified and from my understanding, Ruby-on-Rails leaves many variables to dynamic functions (which is why the code is quicker to write).

Anyways, the reason I'm asking is I'm thinking of learning Ruby-on-Rails and I need to know what people think of it so I can make the right decision.

Are there any Ruby-on-Rails developers here who can vouch for Ruby? How has been your experience in development with Ruby-on-Rails?

Sincerely,

Jerry K
www.JerryKobylt.com (http://www.jerrykobylt.com)

[drhowarddrfine]

Ruby is another language of the week. In 2007 there will be another one. Rails is a framework to make creating apps easier. Pretty soon you won't even have to think to program. Then everyone's code just like MySpace web sites.

[Rang]

Hi,

I'm a complete newbie. Doing everything for the first time and really have no clue what i'm talking about so please bare with me.

how can i create rake task to add records in the table?????????
i created table with rows as name,address,email....
pls help me....

[Scriptage]

Ruby on Rails is supposed to make MVC programming (http://wiki.rubyonrails.org/rails/pages/UnderstandingRailsMVC)easier, but in my opinion it is an absolute dog. If you are interested in using the MVC design pattern you are better off learning XML / XSLT and a language that is proficient in dealing with them (which unfortunately rules out PERL as it's support for XSL is limited). I would use a .Net language (probably C#), however, Java, C++ and PHP can be just as effective; so which ever language you choose to implement the design in the pattern would be as follows:

Model: The business model contains all of your application logic, i.e., retrieves and parses data from the database; returns data in XML format.

View: The GUI comprises of a set of XSL Templates; passes data to the Controller.

Controller: Determines which actions to perform based on information passed by the View, interacts with the Model and parses the XML into a readable format (the View).

Regards

Carl