Ruby on Rails Online Training

Why Ruby on Rails Is Still a Good Choice in 2020

On the cusp of each new year, we’re usually pelted by articles proclaiming the death of this gem of a framework. And while Ruby on Rails is almost 15 years old, it’s nowhere close to passing on from the world of programming.
In fact, there are many use cases where RoR offers a better fit than any other tool. Having delivered dozens of projects in this language since 2010, we know them all too well. So let’s back all of these claims up with some facts.

First Things First

• Ruby on Rails is written in Ruby, a dynamic, general-purpose programming language. Many entrepreneurs and non-developers often confuse the two, thinking Rails when hearing Ruby but rarely the other way around.
• This may be brought on by the fact that the majority of Ruby developers use Ruby on Rails framework for development. Further, Ruby as a programming language really only gained momentum following the launch of Ruby on Rails.
• Rails was created in 2004, and Ruby won the "Programming Language of the Year” award from Tiobe in 2006, despite the language being written way back, in 1995.
  Of course, there are other frameworks based on Ruby, but their popularity with developers, as well as the number of active contributors are both pretty low when compared to
• Ruby on Rails. We’ll take a closer look at that later on in the article.
• This isn’t to say that other Ruby frameworks are necessarily lower in quality than Rails. Quite the opposite, actually—they were built to respond to very specific use cases, and often outperform Rails at them. Rails, however, will be a good fit for the majority of projects that call for using a Ruby framework.

Ruby on Rails Revolutionized the Web Developer World

• When RoR entered the scene in 2005, it introduced a fresh approach to building Web applications. One of the things Rails brought along was the convention-over-configuration software design paradigm that facilitates developer work on many levels—for example, by eliminating the need to write boilerplate code.
• Together with Django, Python’s most popular Web framework released the same year, Rails propagated the use of the MVC pattern and good development practices, such as the DRY principle.
• The Rails way of Web development unshackled devs from the tedious parts of coding, freeing them up to focus on the business features and logic of the app. It also increased productivity and helped developers deliver MVPs and startup apps much faster.

Why Do So Many Think Ruby on Rails Is Dead or Dying?

Almost an urban legend by now, the myth of RoR’s demise is the product of many misconceptions that grew around the framework and the language it’s based on.
Time to dissect them, then.

1. Slow Performance

• While Rails has slower runtime speeds than, for example, Node.js or Golang, this only becomes noticeable with huge products with large-scale traffic.
• And if this isn’t a huge app with a lot of users and requests we’re talking about, Rails doesn’t necessarily have to be the culprit behind the slow speeds—there’s also server architecture or databases to consider.
• With a well-thought-out architecture and infrastructure (a necessity in all large-scale projects, regardless of the programming language), even huge apps, or their parts, written in Rails can be fast. Examples include Basecamp, Airbnb, or GitHub.
• Because Rails does so much for the developer, inexperienced devs tend to make wrong decisions when writing the code. With bad code, the drop in performance is significant.
• When it comes to Ruby and RoR’s inherent performance issues, they are actively being worked on. Ruby 2.6.1, released in December 2018, included performance improvements and new features. Moreover, the developers behind Ruby 3 aim to speed up the language by three times compared to Ruby 2.
• Also, Rails 6.0 is expected to come out in April 2019, packing solutions that simplify building Web apps even more. And since “Rails 6.0 will require Ruby 2.5+,” the framework will have all the perks of the new Ruby aboard.

2. Scalability Issues

• I’ll start by explaining that it’s wrong to blame only the framework for scalability issues and deficiencies in handling many user requests.
• For the application to be able to serve requests quickly, each element in the server system architecture, not only the Web app’s backend, should be configured well and be appropriately performant.
• Ruby on Rails was accused of being difficult to scale when Twitter moved away from Rails to Scala.
• The transition was probably what first sparked the debate around RoR’s scalability issues. Still, let’s keep in mind that we’re talking Twitter-size traffic here.
• So, before condemning Rails, try to identify which element exactly is responsible for the slowdown.
• Available scaling options with Rails:
• code optimization
• service-oriented architecture
• horizontal scalability

3. It’s Mature, Hence Boring

• Whenever a new framework emerges, especially one that brings something innovative to the table, it goes viral and suddenly hundreds of its users and contributors pop up all over the world.
• Then a few years pass, the hype dies down, and what was once cutting-edge becomes much less exciting, intriguing, and challenging. It’s maturing. But maturity does not necessarily have to be boring.
• Maturity means refined code and stable, maintainable Web applications, even if no longer written in a hot, new framework.

Chasing technology trends isn’t always a good idea. Instead of improving business operations, a change to something more popular can actually yield adverse results and increase overhead.Here’s an example of what can go wrong:

• You have Ruby on backend, but Python is the top dog now, so it’s natural to feel like Python might benefit your business.
• Unless your application is as big as Twitter, business benefits from adding Python won’t be big enough to compensate for the implementation costs.
• A better approach is to use what’s available within your current setup and solve the problem with a minimum waste of resources.