Ruby On Rails Reviews & Product Details

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.

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.

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.

Been using RoR for the last few years in 2 different companies and for a few side projects. Ruby on Rails is a great platform for rapid application development. It has a great ecosystem and different deployment options. Lately we use it via JRuby so we have access to the entire Java ecosystem as well. Ruby is a great language. Allows you to do a lot of complex things very easily. Ruby on Rails was a very influential framework. It has led to the importance of ReST and platforms like ASP.net MVC, Groovy on Grails and a few PHP clones too.

Rails has stagnated a bit lately. The problems with business logic are deep and need to be handled separately from Rails. The "Rails way" has deep problems with maintainability because REST is really not sufficient for complex apps. I find the Trailblazer approach great. In addition there are moves towards single page javascript apps and using Rails for only APIs. For a simple API Java might be a better choice for pure API's.

Any custom logic can be put into Rails. I have worked on appointment scheduling, sales systems for custom home builders, purchase order distribution, custom payments. There are no limits. Only super high performance stuff could use a better platform.

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.

It's a great tool for creating MVPs. It's fast and beautiful. Rails code is clean and effective. I also can use free heroku server and it's great. Rails is opensource framework. Documentation is also almost perfect and you don't need to read something else to start coding. There is also some good rails content management systems, e-commerce engines etc.

Dependencies management (but it's mb because i've used php before). What was also important for me is Windows compability, but i know that it's more likely my problem, not rails's :) (I used railsinstaller and sqllite on windows). There are not so many junior dev job offers, so it's hard to find a job, if you are junior developer. Especially if you are not in USA (but it would be fair to say that the ratio of remote work to office work is the best).

Fast testing of hypotheses. I think it's one of the best tools for startups. And also it's secure (most of the times). Also rails developers salary is high, so you don't need to think about finace issues, you can just do what you like to do.

Easy to read, loaded with gems (libraries), and very active community. A game changer when you develop somethings new. It also quite easy to maintain if you follows best practices.

In some situation performance can't match with other framework and of course, big stack came with great RAM responsibility.

We are doing all sort of the impossible things and Rails help us to archive that in a very short time.

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.

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.

* 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.

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.

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.

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.

- 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

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.

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