Ruby on Rails criticism: Deserved or Not - Sloboda Studio

**Related: ** **Pros and Cons of Ruby on Rails** *2) Rails takes up a lot of random access memory (RAM)* *2) Rails takes up a lot of random access memory (RAM)* **True**, Rails can sometimes have a high memory usage. In fact, this issue is especially notable with small-sized projects. Rails tends to take up lots of memory there. … There shouldn’t be any problems with gems that go in Rails dependencies. Although some issues may occur while using third-party gems, this can be avoided by using utilities. *5) There are too many tools and gems* *5) There are too many tools and gems* **Yes,** it can be counted as a disadvantage because an inexperienced developer won’t know which one to use. A variety of choices is not always a good thing. … Luckily, **developers have found some workarounds**. For example, by using **dry-rb**, a collection of Ruby libraries, Rubyists are now able to work with different components in a more flexible way, since each element is divided into separate components. Plus, you can always turn to **Trailblazer**, Ruby’s business logic framework. Just use it on top of Rails for better support. … Even if you succeed, there will be big functionality restrictions. However, low coupling provides easier project support and helps to manage complexity. *9) Hostings for Rails are pricey* *9) Hostings for Rails are pricey* **In a way**, prices for hosting vary in different programming languages indeed. If you compare a hosting for Ruby with a PHP hosting, then sure, Rails would be more expensive. Meanwhile, Python is somewhere in between.