📜 ⬆️ ⬇️

Ruby on Rails: the less functionality the better

In connection with the release of the second version of the Ruby On Rails web development environment, its author David Heinemeier Hansson gave an interview to the press. The main idea that he is trying to convey to users - do not expect much of the functional expansion. Moreover, in the second and subsequent versions, the functionality will be reduced due to the removal and transfer to plugins of little-used and conceptually inappropriate functions. For example, such a fate awaits the Action Web Service element, which is used to create a SOAP web services API. It is assumed that after this, developers will more often use Representational State Transfer (REST) ​​as an alternative.

The Ruby On Rails system should remain as compact, fast and easy to use. David Hansson believes that it is due to these qualities that Ruby language has become so popular and has grown to real competition with such “monsters” as Java and .Net. According to experts, applications that require ten months of development in Java and .Net can be written in just four to six months in Ruby on Rails.

The presentation of Ruby On Rails 2.0 will be held at the RailsConf 2007 conference in two weeks.

In the second version of Rails 2.0, of course, there will be some innovations, but there will be a few of them, because the main task is to consolidate and optimize those functions that are already in the framework.
')
By reducing the built-in functions, third-party developers are stimulated to create their own plug-ins. For example, at the same conference, the official release of the embedded development environment from CodeGear (a division of Borland) on the Eclipse platform will take place. This product has been beta tested since May. Perhaps Sun will release a new version of JRuby, a Ruby implementation for the Java environment.

Created just three years ago, Ruby on Rails is a young program and it has its limitations. For example, Twitter developers claim that their Ruby system is hard to scale, and programs in this language are slow. However, as soon as it was needed, the community of independent developers immediately released the necessary plugins for scaling.

Another problem with Ruby and Ruby on Rails is uncertainty about tomorrow. Since there is no large developer behind these technologies, there is a risk that at some point they will be abandoned and not needed by anyone. On the other hand, the community is unlikely to allow it.

Source: https://habr.com/ru/post/13858/


All Articles