Ruby On Rails Reviews & Product Details

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.