Java vs Ruby on Rails docking

Ruby and rail: Regression framework

Ruby and rail are very concise, very easy, very rich. I can't avoid the continual seeing and hearing the above argument. For example, Bill Walton's rail review on Ruby said: "What would you think if I told you that when you use rail to develop a Web application that is at least 10 times times faster than if you were developing a particular Java framework?"

After experimenting with RNR, I found that this is a very classic framework that accompanies the old technology:

· Ruby is a very powerful language, just like Smalltalk. I choose a static language.

· The constructed material is passive code generation. It's like the IDE wizards or Appfuse. I choose dynamic code generation, or better-no code generation is needed at all.

· Relational Database Center: coded generators and ActiveRecord are thought of first in the table and then in categories. I chose an object-oriented, like Hibernate, JPA, or even Odbms.

· MVC: I'm looking for tools that are better than the old MVC framework update.

Java problems: Java developers

In the Java world, productivity is a matter of culture, not of technology. This is called this is not Java's fault, it's our fault, we as Java developers need to design a very beautiful system, to apply anywhere in the GOF mode, so that any tool can be reused, the three-tier architecture into all our systems and the use of Web servers. We are not looking for the most direct way, so we have no way to find the most direct way. But Java, a very simple language, makes it easy for us to approach software development.

Java productivity: The other way

One way to solve productivity is to use the drive model. This is the development of the model segment, just the model link in our application, we can use the framework to produce all the applications. MDA, Openxava, trails, nakedobjects, Roma frameworks, and Jmatter are all in this way.

Goal

This is the primary interface for the application you need:

Figure I