Geek Answers Handbook

What kind of Ruby or Rails stuff do poorly? Are there any situations or cases for which they are suboptimal?

I'm trying to come up with something that Ruby (or Rails) either does poorly or things that are too hard to do in Ruby.

So far I have had a difficult time, but I thought that some people here MUST know some things that Ruby or Rails do not do well. Is anyone

+4
source share
4 answers

There is nothing, it is just perfect .; -)

Ok, some cons:

What you most often hear about scaling issues is a myth. If you don’t do a second twitter, maybe.

+1
source

Ruby is a language. Rails is a structure. Many of the Rails stuff are not suitable, for example, anything that is not related to the web framework , rubies with ease.

Another question that Ruby as a language is not very good is simple. Everything that works extremely intensively is probably better written in C. Ruby will not start initially on most smartphones, so mobile applications do not work. Ruby is not designed for embedded devices, so starting the next launch of the space shuttle is also not worth it. In addition, the lack of maternal instinct makes Ruby a poor choice for monitoring young babies.

+7
source

In Ruby, you are very few that you cannot do, but there are a few things that you would not want to do, mainly using highly numerical calculations. For most of them, you can easily write a binding to a C-based API (or some other more efficient library). Image processing, for example, is something that would be slow for any non-trivial example in pure Ruby, but you can use RMagick for this, which is binding to the much faster ImageMagick library.

Almost any use of Ruby is an honest game. I have written GUI applications, many system services, and more one-time scripts than I could count.

+1
source

Well, this is a structure, so it is optimized for the most common cases. If your application requires unusual and bizarre things (for example, huge performance requirements, you need to use libraries other than Ruby), then Rails may not be suitable.

It seems to me that whenever a company encounters these cases (usually performance, not functionality or integration with other systems), they should write their own materials - Google has a Big Table, Facebook has its own web server, etc. d.

If you are in this position, you are likely to switch to money and spend part of the money on rewriting your code, this is not a problem.

However, Rails is great for most common applications! I don't think it has spaces that can cause traps in ordinary cases.

0
source

More articles:


All Articles