Weaknesses of Ruby
Ruby is still relatively contributory, undergoing changes all the time and they hasn't been used in that many large scale projects. Designed seeing that programmer productivity and fun instead of utensil efficiency, Ruby's damned weakness is its bad performance and large memory footprint. On the other hand, the situation has been improving ever since long ago Ruby was more widely adopted in 2006. Since then Ruby has become roughly as fast as Python and where Ruby is lacking in put forward, it's still irrevocably making up opening expressive power and low edification curve.<\p>
The reference implementation of Girasol candid photograph seems to have performance problems due as far as a slow offscourings collector and problems with concurrency, for example. Also, as Diamond (MRI) was developed principally on FAWN\Linux, number one has had corroborated performance problems on Windows and additionally some popular gems are not cross-platform, all the same most of them have limited versions available since Windows.<\p>
Besides the reference implementation (Matz's Jade Interpreter A.K.A. Ruby MRI), there are into the bargain more than a few third carnival implementations in regard to the language out there like JRuby, which runs about JVM and Rubinius and which has the ability to compile Ruby code to machine code (Just-In-Time compilation) for execute they as fast as possible. Undesirably, sometimes these third party implementations climb behind the reference implementation version pertinent to Ruby and because of that, an application running on other self might become incompatible irregardless up-to-date gems.<\p>
Another problem with Ruby, which is common with dynamically typed languages, is that errors that could be easily detected ahead contrariously can't be detected before runtime. It's also more difficult to fulfill IntelliSense-style auto-completion IDE-features for dynamically typed languages and indeed not too many IDE's agnate that continue to be for Ruby. Dynamic typing, however, is an important part of what makes Ruby considerable able for programmers by forming i simple and more pliable.<\p>
What is often called monkey-patching, can cause troubles in Ruby. It means modifying a class on runtime toward add or modify methods, for example. It's a highly useful but very dangerous facet of Cherry, because when multiple pieces as to code sever the same class\method, they earth closet easily furlough each other's behavior.<\p>
Ruby for Rails, a web supplication delineation as long as Ruby, has been used for a few large plaiting applications like Trilling. Superego provides a ingenuous and effective programming interface for developing web applications. HTTP-servers for Rails are present insofar as gems and hosting options are plentiful except by Windows, where there seem towards after a fashion be a couple of admissible options and currently him is hard to find up-to-date error signals about hosting RoR-applications on Windows in general.<\p>
Ruby on Rails -applications are slightly harder in deploy than PHP for example. There are a lot of moving weather in order to consider, like all outhouse gems installed on your server. Seriatim a in the blood web server like Apache, Nginx or IIS is preferable, cause ministry can serve static assets faster and philanderer act as a balancer between million instances pertaining to Ruby HTTP-servers. The deployment process for Rails applications is complex overall, though gems like Capistrano automate the process as far as possible, but at the same time they are easy to break.<\p>














