By Ernest | September 21, 2009
For most business owners, it has been advised the Ruby on Rails is the best way to go especially if you don’t want too much technical terminology with reference to the programming included in the whole package.
Known to be an extension of the Ruby programming language, it is a very powerful and enriching programming language. It uses intelligent reflection and discovery to automatically map relational database tables to Ruby objects.
Thus, the application code and the running database already contain everything Rails needs to know. Best of all, it requires less coding, something that is the normal excuse each time a compiled program goes on the blink.
(Source) Script2Please
The obvious need today is to go with the flow of technology as aggressive web applications are being produced here and there. Ruby on Rails has been identified as the best interface software that programmers look forward to today since it simple yet great output makes the world of programming all the more simpler.
You can really install it on any software even on your Windows XP or Vista. With all the ideas of new developmental software up in the air, you can just imagine how many programs from people can be seen after some time especially once they have settled in and mastered this program.

JRuby, YARV, Rubinius, and IronRuby are some of the alternative implementation of the Ruby language as of 2008 with each of them taking a diverge approach.
“JRuby” One of the strong features of JRuby is its capacity to invoke the classes of the Java Platform considering that it is a Java implementation of the Ruby and is closely incorporated with Java.
“YARV ” an acronym for Yet Another Ruby VM, it is a bytecode interpreter developed for the Ruby programming language with the goal of trimming down the execution time of Ruby programs
“Rubinius” it is clean, understandable code that is easy for users to comprehend and extend. It is a virtual machine and compiler for Ruby.
“IronRuby” an approaching implementation of the Ruby programming language that targets Microsoft .Net framework

One of the Ruby on Rails fundamental principle is “convention over configuration.†It aims to reduce the number of decisions that developers need to make as it gains simplicity but not losing flexibility. The simple phrase implies that a developer only needs to indicate alternative aspects of the application. When the convention implemented by the tool you are utilizing equals your desired behavior, you take pleasure in the gains not even having to write configuration files. When your desired behavior digresses from the implemented convention, then you configure your desired behavior. The programmer can work at a higher level of abstraction with all this configuration free approach to programming.
Also known as Single Point of Truth, “don’t repeat yourself†or DRY is a process philosophy seeking to reduce duplication especially in computing. This philosophy stress on that information should not be duplicated because it makes the change more difficult, it can lessen clarity and may lead to inconsistency. DRY is from Andy Hunt’s and Dave Thomas’ principle in the book of Pragmatic Programmer. A revision of any single element of a system does not alter other logically-unrelated elements when the DRY principle is effectively applied. Moreover, elements are kept in sync because elements that are logically related all change predictably and evenly.
Posted in Basics | Tagged DRY, Ruby philosophy |

Rails uses the Model-View-Controller (MVC) architecture just like many other contemporary web frameworks for organizing application programming. Rails is remarkable for its widespread use of the JavaScript libraries Prototype and Script.aculo.us that is significantly used for for Ajax and its graphical interface. And because of Rails’ “out of the box†scaffolding, it can promptly generate most of the models and views necessary for a basic website. Rails has useful development tools built in or already installed like the WEBrick web server and the Rake build system. Rails also originally supported lightweight SOAP for web services and it was later replaced by RESTful web services as it significantly altered to version 1.2.

Ruby on Rails with its noteworthy benefits and real-world applications in production made its web application framework a top choice. And it is not a shocker for Rails to succeed on the abundance of Mac OS X. Ruby on Rails is an open source tool that quickly generates great web applications backed up by SQL databases to keep up with the speed of the web. Members of the Rails core development team work with Mac. A prominent text editor used by Rails programmers is a Cocoa application called TextMate. That is why it is not much of a revelation that Mac OS X has been a preferential application for Rails’ expansion and development.
Posted in Basics | Tagged Mac OS X, Rails |

If Mongrel and lighttpd are not installed, by default Rails will use WEBrick, the webserver that ships with Ruby. All these will guarantee you to always get up and run promptly. Rails will check first if Mongrel exists when you run script/server, then check on lighttpd and would finally fall back to WEBrick which is a small Ruby web server appropriate for development but not for production. Mongrel is a Ruby-based webserver possessing a C component that requires compilation. It is suitable for development and operation of Rails application. Lighttpd is considerably faster than MOngerl and WEBrick but entails additional installation and presently only works well on OS X/Unix.

Ruby Central Inc. is a non-profit organization based in the United States that is committed to support and for the advocacy and promotion of the Ruby programming language. This organization was founded and established by a group of Ruby advocates like David Alan Black, Richard Kilmer and Chad Fowler. Ruby central is the parent of the annual International Ruby and Ruby on Rails Conferences that serves as a presence and contact point of corporate sponsors concerned in supporting and promotion theses conferences and other Ruby activities. Its first project was RubyConf 2002 and ever since, RubyConf’s have been held. Teaming up with the San Francisco-based Software Development Forum to produce the 2006 Silicon Valley Ruby Conference, Ruby central has also become a center for support of Ruby activities.
Posted in Basics | Tagged ruby central |

Ruby on Rails is set to merge with its main competitor, Merb and end up becoming Rails 3:
We all realized that working together for a common good would be much more productive than duplicating things on each side of the fence. Merb and Rails already share so much in terms of design and sensibility that joining forces seemed like the obvious way to go. All we needed was to sit down for a chat and hash it out, so we did just that.
What this will mean in practice is that the Merb team is putting their efforts into bringing all of the key Merb ideas into Rails 3. Yehuda Katz will outright join the Rails core team, Matt Aimonetti will work on a new evangelism team, and Carl Lerche and Daniel Neighman (hassox) will be co-starring the effort to bring all this over. We’ve immortalized the merge with plaque page at rubyonrails.org/merb.
Always give peace a chance, I say.
Source