zehs_sha
چهارشنبه 16 خرداد 1386, 14:42 عصر
y Justin Silverton
Introduction
wikipedia defines ruby on rails as the following:
Ruby on Rails, often called RoR, or just Rails, is an open source web application framework written in Ruby that closely follows the Model-View-Controller(MVC) architecture. It strives for simplicity and allowing real-world applications to be developed in less code than other frameworks and with a minimum of configuration. The Ruby programming language allows for extensive metaprogramming, which Rails makes much use of. This results in a syntax that many of its users find to be very readable. Rails is primarily distributed through RubyGems, which is the official packaging format and distribution channel for Ruby libraries and applications.
I have worked on a couple of projects with ruby on rails and in my experience, it is not ready for large-scale applications and other languages should be considered (asp,asp.net,PHP, or perl) before taking on a project.
Here are the 5 reasons why I am not going to be using ruby on rails for my next project:
1) it’s a buzz language
As a consultant, I’ve come across many clients that only want to use ruby on rails simply because they’ve heard about it in the latest issue of their favorite tech magazine. Just because a language is the latest buzz doesn’t mean it is more powerful a better choice for the job.
2) The language is young
It was released to the public in July of 2004 (source: http://en.wikipedia.org/wiki/Ruby_on_rails#History). Many other languages have a better history and track record.
3) Poor support for IIS
Even though I personally use apache+linux or freebsd, there are still many corporations and sites running IIS. Although there are docs explaining how to configure it properly, the difficulty and lack of information leads me to believe that it is aimed at a *nix crowd.
4) creates dirty code
Here is an simple example of ruby code (it takes the factorial of a number):
def fact(n)
if n == 0
1
else
n * fact(n-1)
end
end
This may work for small scripts and apps, but large applications with thousands of lines of code and hundreds of source files will be very difficult to manage with this type of syntax.
5) scalability
I’m not saying ruby does not scale, it’s more of a question: Does it scale? this one also ties in with #2. I have not come across any large, feature rich, and popular website or service using ruby on rails as its main powerhouse. Until I can be confident that it is indeed possible, I am going to focus my attenion on other languages.
Conclusion
I believe that you should always use the right tool for the job. Many people get caught up in the newest buzz words and languages, but aren’t looking at the overall picture. Ruby is a promising language, and works well for small scripts and utilities, but shouldn’t be used it large-scale applications until it is a proven technology
http://www.whenpenguinsattack.com/category/ruby/
.
Introduction
wikipedia defines ruby on rails as the following:
Ruby on Rails, often called RoR, or just Rails, is an open source web application framework written in Ruby that closely follows the Model-View-Controller(MVC) architecture. It strives for simplicity and allowing real-world applications to be developed in less code than other frameworks and with a minimum of configuration. The Ruby programming language allows for extensive metaprogramming, which Rails makes much use of. This results in a syntax that many of its users find to be very readable. Rails is primarily distributed through RubyGems, which is the official packaging format and distribution channel for Ruby libraries and applications.
I have worked on a couple of projects with ruby on rails and in my experience, it is not ready for large-scale applications and other languages should be considered (asp,asp.net,PHP, or perl) before taking on a project.
Here are the 5 reasons why I am not going to be using ruby on rails for my next project:
1) it’s a buzz language
As a consultant, I’ve come across many clients that only want to use ruby on rails simply because they’ve heard about it in the latest issue of their favorite tech magazine. Just because a language is the latest buzz doesn’t mean it is more powerful a better choice for the job.
2) The language is young
It was released to the public in July of 2004 (source: http://en.wikipedia.org/wiki/Ruby_on_rails#History). Many other languages have a better history and track record.
3) Poor support for IIS
Even though I personally use apache+linux or freebsd, there are still many corporations and sites running IIS. Although there are docs explaining how to configure it properly, the difficulty and lack of information leads me to believe that it is aimed at a *nix crowd.
4) creates dirty code
Here is an simple example of ruby code (it takes the factorial of a number):
def fact(n)
if n == 0
1
else
n * fact(n-1)
end
end
This may work for small scripts and apps, but large applications with thousands of lines of code and hundreds of source files will be very difficult to manage with this type of syntax.
5) scalability
I’m not saying ruby does not scale, it’s more of a question: Does it scale? this one also ties in with #2. I have not come across any large, feature rich, and popular website or service using ruby on rails as its main powerhouse. Until I can be confident that it is indeed possible, I am going to focus my attenion on other languages.
Conclusion
I believe that you should always use the right tool for the job. Many people get caught up in the newest buzz words and languages, but aren’t looking at the overall picture. Ruby is a promising language, and works well for small scripts and utilities, but shouldn’t be used it large-scale applications until it is a proven technology
http://www.whenpenguinsattack.com/category/ruby/
.