Ruby on Rails Reviews & Product Details

- 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 Review collected by and hosted on G2.com.

- 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 Review collected by and hosted on G2.com.

How easy it is to generate documentations.

How human readable the code is.

How easy it is to keep your code organized.

How fast it can be to build solutions and measure results.

How it encourages the user of needy practices and take advantage of software engineering principles. Review collected by and hosted on G2.com.

While Ruby and Rails work on Windows, a significant number of gems were developed with Unix in mind without being tested on Windows. This force the developer with a Windows system to either install a Unix vm or find away to deal with incompatiblities. Review collected by and hosted on G2.com.

Rails is an old enough framework, but it's still a good choice for nowadays project. It's itself a collection of best practises. Not to mention it has a big ecosystem. Both of them can boost up the projects for startups. Even you can not find the gem to solve your domain problem, you can build your own wheel with Ruby (with some low level gems), it's a joy journey.

Rails also inspires many other frameworks, that means if one day you switch to another language & platform, you can still use some of the experiences. For example, you can reuse 80% of the experience in Phoenix framework if you care about concurrency. Review collected by and hosted on G2.com.

Rails is not for newbies. It's productivity based on "I'm experienced about web and I know Rails has solved lots of tricky problems", but not "I have less experience so I need a framework to help me to keep away from those details". It's not actually a disadvantage. But be careful not to shoot your feet.

A real problem is, you need to judge what to use and what not to use from a lot of gems. Some of them are awesome, but maybe not very fit for your project. You can build a prototype quickly by using lots of 3rd party gems, but later on you may find the code is hard to modify and upgrade. Choose wisely for Rails built-in parts and 3rd party gems.

Rails is extracted from Basecamp, that also means some of the solutions are affected by Basecamp. Many people like to call them the "Rails way". It's not good for everyone, so you still need to judge. Review collected by and hosted on G2.com.

The thing I like most about ruby on rails is it's Conventions Over Configurations mindset. Everything in rails has a convention of where to place stuff, how to do it etc. If you're following the conventions of rails, the framework lift you a lot of heavy burdens. Review collected by and hosted on G2.com.

The drawback of opinionated conventions. Most of the rails conventions are great and reasonable for normal web development process. But business needs are not always identical and there will come a time we have to do things that rails didn't configured to do. This is the moment rails' magic is dispelled. You have to look into a lot of stuff just to customize something not the rails way. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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 Review collected by and hosted on G2.com.

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 Review collected by and hosted on G2.com.

My favorite part about Rails has to be the "opinionated" part of it. Yes, you may find yourself battling the framework for some unconventional things, but the time saved using it is enormous! This was also a huge benefit when learning the framework because all tutorials stay consistent with where code goes and configuration. routes go in routes, models are in models, views in views... Comparatively, when trying to learn node.js/express.js, you could find a tutorial on posting a form, then another for handling files, and the server setup is completely different. Review collected by and hosted on G2.com.

I dislike the asset pipeline when dealing with frontend framework, mainly angular.js. Things can get messy fast here in my experience. There are some great resources best practices for connecting angular and rails though. Just the learning curve of angular mixed with integrating it into rails turned me off from using it one of my projects. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Ruby syntax is very friendly and it encourages users to write the code like a story. Object oriented model is the core of Ruby it allows to apply OOP principles in a very easy manner. Moreover it opens new horizons with the full power of meta- programming. There is a joke: when you use lightweight framework for the project after some time you would have a huge monster that will try to do the same things as rails do but in a very pervert way. Rails is a very stable framework that combines one of the best ORM I have ever seen, easy routing module and nice aggregation of useful modules, that make life easier when you are thinking about the security, scaling and maintaining of your application. Review collected by and hosted on G2.com.

The real pain for me was the magic, that is going inside some rails parts. I have a really interesting time debugging it during migration from rails 3.1 to rails 3.4 Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

In some situation performance can't match with other framework and of course, big stack came with great RAM responsibility. Review collected by and hosted on G2.com.