When I selected a language in the project in the early stage, I hesitated for a long time in ror and Django, and finally saw an evaluation.ArticleI also mentioned that Django is twice as efficient as Ror, so I chose Django.
After a period of exploration and practice, I used only one week for the development of this small project, including a lot of work on the page. It can be seen that Django's development efficiency is indeed quite high. In addition, because the current understanding of this framework is not very thorough, it may beCodeStill need to be improved, because there are still a lot of repeated code.
Today, we suddenly saw the ROR version 1.2, which is a considerable reconstruction for the previous version 1.1.6 and has changed the architecture idea. I learned from this article that the HTTP protocol has four methods, and I have never heard of the put and delete methods. However, since browsers do not support this, it is no wonder.
However, Ror simulates the two methods by adding parameters to the post method, so it forms get-> select, post-> Create, put-> Update, delete-> Delete is a clever correspondence between the HTTP protocol and database operations. That is to say, through HTTP, we can find the direct crud correspondence.ProgramWhat are the problems? All our create and update Methods Use post, and delete must also use post (or get ). With this new method, we only need to know the object to be operated, and the rest is to map the controls on the form with the attributes of the object.
Although it sounds quite advanced, I feel scared. I am not a person who fears new technologies, but I am still worried about the future of such a great change. Of course, it may not be a big problem to make ror popular today.
I think the real popularity of ROR is the complexity of its release. It must at least achieve the publishing complexity of PHP, so that it can be widely accepted by virtual host providers, and then be accepted by developers. After all, virtual hosts are the mainstream in website development.