SWOT analysis of Ruby on Rails

Ruby on Rails SWOT analysis

According to Wikipedia (https://en.wikipedia.org/wiki/SWOT_analysis):

SWOT analysis (or SWOT matrix) is an acronym for strengths, weaknesses, opportunities, and threats and is a structured planning method that evaluates those four elements of an organization, project or business venture.

We’ve got used to see SWOT analysis for projects, companies or even people. But why not to try to apply it to a framework? It was invented in the 1960s, so it’s rather an old technique. On the other hand, it gives short and presides description of the topic. Now, when we have more and more discussions whether Ruby on Rails is fading (or even dying) it makes sense to use some tool to check it.

SWOT analysis graph

In theory, SWOT analysis describes:

  • Strengths — what are the strong points that gives an advantage?

There are two interesting perspectives in analysing above points:

  • Strengths and Opportunities are helping as, whereas Weaknesses and Threats do the opposite,

Usually we don’t have an impact on the environment, so the best strategy here will be to maximize our strengths, minimize our weaknesses and exploit existing opportunities.

That’s the theory. Now let’s see how that analysis can look like for Ruby on Rails framework in 2017.

SWOT analysis of Ruby on Rails

Strengths

  • fast development — one of the reasons I came to RoR, it’s a great tool when you start a new project and want to see results soon

Weaknesses

  • consumes a lot of resources (CPU, RAM) — although new versions try to improve that, Ruby and RoR have hard time competing with other technologies in that area

Opportunities

  • a lot of existing big systems — there is a need to maintain them, but also provide some more advanced solutions when it comes to architecture, deployment, CI etc.

Threats

  • new languages or frameworks — Elixir with Phoenix framework is a new kid on the block and many Ruby developers already started using it

Summary

Ruby on Rails still has a lot of strengths and still is a very popular framework (so Ruby is as a language). Undoubted advantages are: fast development, great community and stable position on the market. From the other hand, I have an impression that after many years of its existence, RoR still has the same weaknesses. Maybe only levels of these weaknesses changed. I cannot say the same about threats. 10 years ago there was a danger of not becoming a “mainstream” technology and being forgotten. Today, RoR has to compete with other technologies that wants to solve different (and totally new) problems of (mainly) web programming. These technologies wants to be more attractive to the developers to get on popularity.

In my opinion, saying that Ruby on Rails is dying is far from the truth. If RoR is able to maximize its strengths, minimize weaknesses and use opportunities, it will posses its position for a long time. But how this can be achieved?

  • by being attractive for these who needs to choose fast development

Want to know first about new articles from that blog?

Subscribe to my newsletter now! — http://eepurl.com/cVPm_v


If you like this article and consider it useful for you, please support it with 👏.

kkempin’s dev blog

Dev and life blog. Thoughts about programming, design patterns, Ruby and life.

Krzysztof Kempiński

Written by

IT expert. Ruby on Rails/iOS/Elixir programmer. Blogger. Podcaster.

kkempin’s dev blog

Dev and life blog. Thoughts about programming, design patterns, Ruby and life.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade