How do you choose between rails and grails?

The various comparisons between rails and grails have not stopped since rails and grails have entered people's eyes. Recently Stephan on its blog with rails and grails working trend charts. As you can see from rails and grails work trends, rails is in a fast-growing period, and grails is a relatively slow-rising trend.

But he did not comment too much on the map, as he said: "If you want to comment on this trend, I think it's free." There has been a lot of discussion about it, and everyone is in disagreement. "

From another diagram--google the trend chart, we can look at the people's focus on rails and grails two topics:

Rails		1.00
Grails		0.02

As we can see in the picture, rails has been in a "rapid rise" since 2005, and this year the momentum has slowed. And Grails has been in a relatively slow growth process since 2006.

From the two graphs we can see that rails is still relatively hot, but grails is also growing. From a technical point of view, what is the best of these two? And how do we choose? Earlier Matt Raible expressed his views in his blog, "Grails vs rails--my thoughts."

On the maturity issue, Matt raible that:

All of them are excellent development architectures. Rails is a bit more mature, but creating environments is pretty painful (especially on Windows). For Java developers, Grails is easy to create. What Grails needs to improve is hot publishing and error recording stacks, but these are probably the problems with the groovy language, and the error-recording stack is miserable-rarely indicates the number of classes and rows in the first few lines.

On the question of how to choose between rails and grails, Matt Raible said:

...... Both have the fun of programming and have the ability to greatly improve development efficiency. If you are familiar with Hibernate, Spring, Sitemesh, and JSP, then you should learn grails. If you are proficient in these techniques, you will be able to learn grails within one hours. ......

Is there anything that rails can do that grails can't do? That's not what I can tell you. I think it depends on the enthusiasm of the developer and the choice of the development team. If you're a senior Java developer and like the ecology and its tools, it's more intuitive to choose Grails. If you're a senior PHP developer or feel bad about Java, you might prefer rails. For two development frameworks, they all have one thing in common-learning a knowledge that will actually teach you another. They are so similar in so many ways that their knowledge can be transferred to each other.

Feng (Hivon) has translated "Grails vs rails--my ideas" into Chinese in his blog, and interested readers can click here to see the full translation.