Ruby rails Design Philosophy

Rails calls the Java method XML sit-ups ).

Rails is a complete, open-source web development framework with more happiness and lessCode.

The entire framework runs through the dry (do not repeat) principle. For example, after a database table is defined, the class name and object attribute name are automatically determined. Friends who have used hibernate know what I'm talking about (You may say XDoclet, so you don't have to learn it ).

Low learning cost, no need to learn various XML styles (friends who have studied struts, spring, Hiber, webwork, ant, and Maven know what I'm talking about ), you only need to learn the ruby language.

The joy of programming comes back, without compilation and deployment, that is, modification, and all the complexity is hidden inside the framework.

Do you feel its philosophy? Install it on your own.

========================================================== ===

For comparison, the following text is from the homepage of the rails Website:

Rails is a full-stack, open-source Web framework in Ruby for writing real-world applicationsWith joy and less codeThan most frameworks spend doing XML sit-ups

Being a full-stack framework means that all layers are built to work seamlessly together. that way you don't repeat yourself (dry) And you can use a single language from top to bottom. everything from templates to control flow to business logic is written in ruby-the language of love for industry heavy-weights.

In striving for dry compliance, rails shuns configuration files and annotations in favor of reflection and run-time extensions.

This means the end of XML files telling a story that has already been told in code. it means no compilation phase: make a change, see it work. meta-data is an implementation detail left for the framework to handle.