Ruby On Rails Reviews: 4.5/5 — Highly Rated

The community surrounding Rails is vast. This provides a great array of tools that people have built to make developing for Rails much easier. It also means there are people using Rails in a wide range of applications. This feeds back into Rails development, making it a tool that works in many situations. Rails also has a vibrant testing culture. This makes for more reliable products that are well built. It is so easy to do TDD using Rails. This has saved me many hours of hair pulling as every aspect of the products is tested. Overall TDD has improved our release cadence and reduced our code churn significantly.

The Long Term Support is lagging behind what one would expect from a paid product. This is obviously because it is an open source community maintaining the product. However there are paid solutions people can buy into for LTS.

We are working to solve problems relating to Christian Ministry as it interacts with technology. As the most significant advancement since the printing press, computers are simplifying the way we do donor management, outreach, internal communication and much more. With so many cool things we could make to advance the cause of Christianity, we needed a tool which would enable us to do rapid, reliable software engineering. Rails has provided us with the capacity to write fast, write once, write TDD software.

I like the conventions. If you can think correctly then you will find everything there in Rails. It recommends all the best practices for your applications. Another best thing is the community. If you search for anything, in 98% cases you will find it with 1/2 attempts.

I'm biased a lot with Rails, so everything looks good to me.

I have developed wide range of applications, exploiting its gems and as a result rapid development.

Rails favors convention over configuration. This means that, out of the box, it suits a lot of the modern web developer needs. We have used it for both API servicing a single page app, microservices, and traditional Rails app. The defaults are very sane and aimed at giving everyone a good experience.

With such a huge project, it can be hard to get into open source contributions. Rails tries really hard to fix this, but it's still a reality.

We have shipped traditional applications, single page applications, micro-services, etc. We server high expectation SaaS space.

The ease of development and creation of web applications.

Wish there was a more documentation to figure out complex objectives, but that's way of software development.

We solved a problem in our company by developing a web app in rails to manage customers & their jobs(work orders). To create work orders & also log and print the workorders off.

It allows us to quickly build out, test, and iterate on features. This is enabled by convention over configuration, a great open source community with a ton of gems, and easy-to-setup hosting platforms.

Community gems are unreliable and often become outdated and abandoned by the original developers. Ruby is slow and scaling to meet the needs of a growing user-base is expensive.

Call tracking, intelligent routing, and analytics. We were able to build out a product and bring it to market very quickly for minimal cost.

It's ease of use and how fast you can put together a working website.

Convention over configuration is OK, though when something not standard needs to be done is sometimes painful.

From small to medium sites, mostrly for small companies or individuals.

What I like most about this web framework is how fast I can make a page or web application using ruby ​​programming language and simultaneously handle the frontend and backend as a single in the same environment; this makes it agile and magical. Also, over the years, I have made this tool part of my day-to-day functions at work since I do not need more tools to interact with the database or the console of my project; if not, I can achieve this in the same environment. It is a tool that integrates with any operating system but for me it is more comfortable to use it in Linux operating systems such as CentOS or Ubuntu, they are the two distributions that I use and at the moment it is easy to configure and to be able to prepare the environment which makes it even friendlier and the best option when selecting an IDE for projects in Ruby or Rails.

what I don't like sometimes is the handling of javascript and some javascript gems that don't work well, but in new versions this has been improving. Another issue is the cost, perhaps some developers cannot buy it at first, which makes it a tool for companies, there should be a version for independent developers with low resources or who are just starting out

We have made several applications in the company and this framework has helped us a lot to speed up these developments and at the same time to have a quality product and more now with the management of APIs

- Building Web application quickly. - Lots of useful gems - Provide lots of resources for working and researching. - Documents and Tutorials are detail and updated. - Large community with strongly support

They bring "magic" to the framework that it is hard to control when the app becomes bigger.

Building webapp fast enough to show the features, improvements for my projects

Very Easy to learn. Even beginners can design well functional websites with-in a few days using Ruby on Rails. There are very good tutorials for your help. Development is very fast compared to other frameworks. Very supportive and active community. Regular updates on Ruby on Rails Free Third Party Packages (GEMS) Building Minimum viable product is very time efficient. Great testing support

Performance is not that good when the application grows and reaches scales of millions of users. If the app is big, it takes a lot of time doing simple stuff. So it's like a trade-off between performance and ease of use.

I used Ruby on Rails for a couple of projects. One of them was to design a portal for automatic synchronization of data center inventory. I spent less than one week to set up the whole system and able to design a working solution as most of the desired functionalities were available in terms of libraries. Feasibility testing was also very easy and development was very fast.

It has a logical MVC framework that has a LOT of features.

It's so fully featured it can be hard to know if what you are looking for already exists as some one line command. Most of my time was spent figuring out if something was already implemented internally.

We were making a single page internal monitoring application.

I think the best in Rails is the way that everything you expect to have is there. And the great community behind the framework. There is a loot of tools (gems) that help you in the process of building a great software. And there are some others tools that can be used to improve the performance or even to improve the way you do the code.

The speed, in comparison with other web frameworks the speed is not the best.

I doing web pages, so it helps me doing that. Currently working on several products and Rails help me a lot from the start because it's really easy to setup, and the is easy to continue with the maintenance of the product if what you do it good, otherwise you can get in a mess.

Convention over configuration concept. Usual features for web applications are available in a box way.

Many things happens hide from the developer eyes, this can be dangerous for inexperience programmers.

My team is building the world's best hotel metasearch using Ruby on Rails. Productivity in a test-driven web application.

Ruby on Rails is easy to learn. You can go from knowing nothing about it to a full blown web app in less than one day. You should know how to program, of course. But the point is that it's easy to use and time to deploy is quick and relatively painless especially with a tutorial, something like Pragmatic Ruby is a good one.

It's slow. Once you have a big app, it can be bloated, and take a lot longer to run things than if say, it was all in C. So there is a compromise, between easy of use and performance. But, the bright side is that there is an active community constantly trying to improve Ruby on Rails and make it better, and faster.

Have created a web app with Ruby on Rails that thousands upon thousands of users use daily to improve their lives.

We use Rails as a web API for our mobile app. It has many tools right out of the box and has many conventions that makes many configurations unnecessary, which make it very quick and easy to deploy. The Rails has an awesome documentation and a community is enormous, and just about every beginner question has been answered, this makes it very beginner friendly despite the poorly documented underlying language Ruby. Because of the size of the Rails community, there are many third party gems that cater to your needs.

The "conventions over configurations" philosophy behind Rails can also be frustrating to some developers looking for a more customizable solution. For example, as a web API, Rails has a simple-to-use JSON parsing tool as long as the JSON structure mirrors your underlying models. However, if you want to create custom JSON, this can result in extremely verbose and ugly code.

We use Rails as a web API for our mobile app, this includes using Rails to communicate with the database, and other services that we use, such as ElasticSearch, Amazon S3 etc.

* Easy to setup. * Lots of tools (gems) to choose from * Very flexible, works with many frameworks * Asset pipeline is really nice * Great community - very large and active. * Still under very active development. * It's free. * Good performance. * Lots of good assumptions, promotes good application structure. * TDD

* ActiveRecord - it's good for people who are new to this field. But it's really easy to fall into its traps. * Scaling can be tricky, especially for newcomers. * Doesn't enforce good practice. People can easily write bad code to get things done.

A high performance web based application that serves both internal and external users. Connects to multiple databases and integrates with data analytics application to run data analysis and generate mass amount of pdfs. Integrates with 3rd party APIs.

The convention over configuration mentality is the best thing about Rails. I have worked at so many places where they used their own framework concoction or it grew up organically, and you spend the first weeks just learning the framework, and then the rest of your work-life trying to solve problems in that framework that have been solved by way smarter people than you. This is what Rails solves in a simple, easy to learn, great documentation and scalable way.

The sluggishness of the framework. It's definitely plenty fast for most use cases it's just that I know I'm wasting a looot of cycles on the Rails framework. It's totally worth it and hardware is dirt cheap, it's just that my service is not so revenue intensive so any corner that can be cut is worth looking into.

I use it for every new and current app that I am maintaining and using as a hobby project. Have worked at large-medium sized corporations that used it for hosting a customer facing dashboard and a sales website.

Convention over configuration. Easy to get a web project up and running with a nice framework to work in.

Not scalable for large web projects. Although convention over configuration approach can help speed up development for most projects, it can sometimes get in the way when you have requirements that don't "fit into the box" that Rails provides.

Custom software that doesn't fit into the box of a standard CMS. Have done other projects with more varied requirements as well.

What I love about Ruby on Rails is that it's so easy to just start working on something an get things running fast. We have build fully running products in just a few weeks from inception.

Rails can sometimes be quite intimidating for someone who has just started out, especially if they are from a background of non-scripting languages.

We are building platforms that make business for users much easier by consolidating all their work in one place. The best benefit is the speed that allows us to go through the learning cycle really fast.

- based on Ruby, the most flexible and up-to-date of all programming languages that are in common use today - quick to set up new projects with solid testing and security

- some core features don't scale and become unusable in very large projects, so you end up replacing them or working around them - there are still some rough edges in the latest version, such as modified Ruby core classes or errors pertaining to advanced database features

- hosting a complex community and donation website - metaprogramming features help setting up diverse payment service APIs - permanent change and refactoring is relatively easy thanks to good migration and testing frameworks

The extensibility is remarkable. The Ruby on Rails gem community is still thriving. I have not run into many problems where gems were out of date, or didn't work as intended most of the time. Rails security appears to be strong especially with the default options that help prevent common vulnerabilities like CSRF and XSS.

The learning curve when first getting started is relatively steep. It takes a while to get used to the asset pipeline, and some of the configuration that's required to move on from a simple app.

I currently develop two Rails products. One is an internal application developed for a security company, and the other is a public facing app called Preferred Athlete Scouting Services. The former solves a problem for our company relating to generating vulnerability reports to our clients, and sharing/collaborating on projects and reports between employees. The latter is a basketball player management system that provides access to important information regarding potential women's basketball recruits to college scouting programs.

I like that it is relatively simple to start an application. From starting you first dev instance of the app to pushing it to a production server always seems fast and efficient. The flexibility of Ruby on Rails allows you to incorporate a variety of existing web technologies into one app. Whether that is Database related or front-end framework related it is quick and easily to integrate existing technologies and create a robust application.

I have few complaints about rails. The documentation can always use work I suppose.

You can create fully customized web applications that are scalable and dynamic. I have solved clients problems with ticketing services and online ordering. The benefits I have realized are strongly related to the database relationships you can create with Ruby on Rails models and controllers.

I been using Ruby on Rails for years. I am a senior level professional software developer. I was doing JAVA before. I can tell you that Ruby is much more productive than JAVA. More importantly there is a way of Rails, if you follow the convention there is less room for errors. I like Ruby on Rails it is : - reliable with huge community - productive - creative - easy to start - cost effective

Well there is limitation of it. Currently it is in a strange position with JS on the front-end. Mainly because most the developers in the Rails team are kind of old school and still try to do web page instead of web app. Nowadays i see Rails more of a API server side than page rendering framework. So to sum it up: - strange relation with front-end JS development at the moment

I been working in all sort of business really. Both startup and enterprise. Ruby on Rails is really a cool framework it definitely more productive than many other choices. - low cost - more productive - small team - well maintained projects - good culture in the community

It is a very productive environment, many libs and gems to save time and keep developer happy. It is a very easy to use framework. There is a gem for almost anything you need to create. The rails guides are concise and very detailed. It is an open source project so you can go directly to source code to understand how does it work. It has a great community and it is a top programming language on github.

There are too many magical methods and conventions, sometimes you need to go directly to the gem code to understand how does it works, the documentation for most of the gems is minimal.

A platform for online education. There is a dramatical increase on my productivity compared with other techs like Java or PHP.

Convention over configuration is the best thing that i've seen in ROR

Little slow compared to other, so i can say performance.

Using RoR makes us develop web applications build faster than ever before. Training new employees is like peace of cake.

It's very easy to quickly generate all the pages you need with rails g scaffold. it neatly organizes the file structure for you and reminds you to test. It takes care of linking the files for you and there are a tremendous amount of packages which will do most anything you need.

Ruby/Rails is slower than a python/Java, there is no auto-refresh and it is a bit obvious that it was not generated for a Single-Page application which consumes Ruby on Rails API. Things like JSON web token are not easily done.

Enterprise level permissions and granular control over routing on the front-end.

The tooling rails provides is second to none.

Beware the amount of dependencies the gems you use introduce as that can be a source of complexity.

We built our entire stack in Ruby on Rails and no complaints so far. There are things it abstracts away from you that have cause problems in the past. Implicit ordering and other such features. However, those minor problems don't take away from the fact that we can get new engineers up to speed incredibly quickly.

Ruby on Rails makes it fast to bootstrap your product and get an MVP running for a small startup. If you're in a larger company the Rails monolith allows you to enforce standards like default database structures, and routing patterns. Ruby Gems make it trivial to add additional functionality to your environment and amazing testing frameworks like Capybara and Cucumber make TDD and BDD a breeze. Although still relatively young at under 10 years old, it's been battle-tested by companies like Twitter and Github. There's something to be had for developers of any level.

Because Ruby on Rails enforces standards, it makes it difficult to sometimes tailor your platform for specific needs; there's the "Rails way" of developing and deploying which can be drastically different than what developers may be used to. Additionally, the monolithic nature of Rails made it difficult to use Rails as a back-end while employing a front-end like Ember.js. Active Model JSON Serialization has alleviated some of this stress and Rails API has been merged into the upcoming Rails 5.0 release making this less of a concern.

Ruby on Rails has allowed us to develop products for customers in record time and enforce standards across our development practice. Our development team has been able to congregate easier around a methodology and embrace code reviews and Test Driven Development.

Ruby on Rails is an excellent choice for developing simple applications or early stage business products due to its full-stack scaffolding capabilities. It provides developers with the ability to quickly get up and running without having to write a lot of code. This means that developers can focus on the functionality they need in order to create their product or application, rather than spending time writing boilerplate. This is amplified drastically by utilizing IDE and intelli-sense tools like Github co-pilot. Development speed is incredible. The framework also has fantastic support from its creators at Basecamp, including various auxillary libraries like Stimulus JS. They continue to release updates and new versions, as well as providing helpful documentation and tutorials that make it easier for new developers to get started. Additionally, there is a thriving community of experts and professionals who are always willing to lend a hand when needed.

On the flip side, Rails has a lot of "philosophical conventions" that doesn't necessarily match with modern web paradigms and also allows critical parts of the website functionality to happen magically. The later is only a problem in the early/middle of adoption, as the debugging can be time-consuming and demoralizing and as a result you'll learn to make fewer mishaps. Pairing Rails with a solid IDE and a tool like Github Co-pilot significantly reduce the painpoints.

Rails provided a quick and efficient starting point for launching a website product. Since the business is in very early stages, the framework fits nicely to provide flexability and speed without terrible overhead costs.

Ruby on Rails is great for rapid prototyping. Quickly scaffold out a prototype app in minutes and get running live!

Sometimes it can give me errors, but most of the time it's smooth sailing.

Ruby on Rails provides a comprehensive coebase that covers a variety of technical needs.

The Ruby language is truly the best feature of the Rails framework, but the contribution of David Heinemeier Hansson has been to exemplify the idea of 'convention over configuration'. When working in Rails, there is almost always a clear and efficient path to a solution (within the confines of web applications, at least). This makes Test-Driven Development very attainable, since the components needed for a new feature are easily worked out before the feature is built. This, in turn, expedites the creation of new applications and the maintenance of existing ones because it permits safe assumptions and expectations about organization.

Sometimes the creators of Rails take convention-over-configuration a little too far, resulting in undesirable libraries and limiting patterns being included with the framework. This, I feel, has made some trending concepts and architectures (SPAs, for example) unnecessarily complicated to implement without relying on other technologies.

Recently, my company required a RESTful JSON API for an Angular application. Adapting the existing application to this use was a breeze due to consistent patterns and organization. I have repeated this experience with numerous feature requests, and picking up where someone else has left off is often trivial.