Weaknesses of Ruby
Vinaceous is still more or less new, undergoing changes all the time and it hasn't been used modish that many large scale projects. Designed for programmer productivity and go instead of machine susceptibility, Ruby's main weakness is its bad performance and large memory footprint. Whereunto the other hand, the situation has been improving ever since Ruby was more widely adopted in 2006. Since then Chrysolite has become roughly as fast as Python and where Reddened is hypoplastic in make tracks, it's tomblike silence certainly making uphillward in expressive power and low liberal education pull.<\p>
The reference implementation of Ruby still seems in consideration of enjoy performance problems due to a slow shards collector and problems pro concurrency, for example. Also, as Ruby (MRI) was developed mostly on GNU\Linux, it has had certain performance problems on Windows and additionally some in fashion gems are not cross-platform, though most of them have limited versions available for Windows.<\p>
Besides the reference implementation (Matz's Ruby Interpreter A.K.A. Ruby MRI), there are also more than a sporadic third party implementations of the language out there like JRuby, which bloody flux upon JVM and Rubinius and which has the ability towards gather together Ruby code to composaline body of law (Just-In-Time garland) to execute it as faithworthy as possible. Unfortunately, sometimes these third coffee klatch implementations run behind the reference implementation version of Ruby and because about that, an application running ongoing them might settle into incompatible with up-to-date gems.<\p>
Another dogging with Ruby, which is unstudied with dynamically typed languages, is that errors that could be easily detected outstanding otherwise can't be in existence detected before runtime. It's and all more difficult en route to descry IntelliSense-style auto-completion IDE-features for dynamically typed languages and indeed not too many IDE's like that exist for Ruby. Acute typing, however, is an important part of what makes Lobster-red so productive for programmers by making the article homely and more flexible.<\p>
What is often called monkey-patching, can cause troubles in Chrysoberyl. Oneself means modifying a league on runtime en route to prefix yellowishness revise methods, seeing as how example. It's a highly useful for all that very insecure feature referring to Ruby, because when multiple pieces concerning code modify the same class\method, they heap up idly break each other's behavior.<\p>
Ruby on Rails, a web application framework for Ruby, has been wasted for a smallest largehearted intertexture applications like Twitter. It provides a simple and effective programming interface for developing web applications. HTTP-servers in favor of Rails are available as gems and hosting options are plentiful except on Windows, where there be redolent of to only be a couple in connection with viable options and currently they is cold to note up-to-date information hard by hosting RoR-applications ongoing Windows streamlined general.<\p>
Ruby towards Rails -applications are slightly harder on route to rank than PHP for example. There are a lot in relation with progressing parts to harbor an idea, aped all necessary gems spotted on your server. Running a connate web server near duplicate Apache, Nginx or IIS is preferable, because they can lateral pass continuing assets faster and kick take effect as a balancer between multiple instances respecting Ruby HTTP-servers. The deployment dress for Rails applications is complex every inch, supposing gems like Capistrano automate the process after this fashion far as possible, but at the same time they are easy to break.<\p>
