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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
The ease of development and creation of web applications. Review collected by and hosted on G2.com.
Wish there was a more documentation to figure out complex objectives, but that's way of software development. Review collected by and hosted on G2.com.
The best part about Rails, is the community. It is a constantly evolving framework built in a very easy to understand language. Its also great for small teams as everything you might need to make a web application comes built in. From connecting to databases and handling data objects, to rendering views and handling sql injections to international languages. Ruby on Rails a complete package of everything you need to make a web application Review collected by and hosted on G2.com.
There is a lot of magic in Rails, by this I mean sometimes things just happen and you have no idea why. Furthermore, Rails has a lot of the same problems as Ruby, It's slow and gives the developer a lot of freedom to make a lot of mistakes. It also doesn't scale past 30 / 40 engineers unless you really know what you're doing. It becomes hard to maintain, slow and just a pain over all. Rails also still uses the MVC which a fairly outdated way of creating web applications as more people move to single page applications built with Node Review collected by and hosted on G2.com.
If you are writing a big enough webapp I believe it's a good framework. It makes it easier to get started without configuring anything and it gives you a very good mvc based directory structure which can be a pain to configure for frameworks like Sinatra. There are lots of libraries that support ruby on rails integration out of the box so that's always a good thing.
Another good thing about Ruby on Rails is the community. You can almost always find a solution to any problem that you are looking for and that makes development a lot faster. And I love the generators that come with the framework; boy do they save time! Review collected by and hosted on G2.com.
Personally I don't like to start with so many things in my app. I have developed both using Ruby on Rails and Sinatra; my first instinct is to use Sinatra, because it's simply a very lightweight framework and I can configure/add things as I need them. Review collected by and hosted on G2.com.
- minimum time requirement for web development
- one of the fastest growing community
- gem based support
- quick and easy way to develop large scalable website Review collected by and hosted on G2.com.
- comparatively less support in terms of multi threading
- not enough tutorials for rails 4
- Initial learning curve requires a little more effort than other languages Review collected by and hosted on G2.com.
I like the fact that I can create applications very quickly, that I do not have to deal with too many technical details and I can focus on my business domain problem. Review collected by and hosted on G2.com.
I do not like the fact that does not enforce various object oriented patterns. For example, the decorator pattern. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
I'm biased a lot with Rails, so everything looks good to me. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
The framework is strictly MVC based. Each new user can build a web application with in 20 minutes. The ruby language is user friendly. Review collected by and hosted on G2.com.
Ruby on Rails framework will load too many things at the very beginning. Some of them will never be used by developer. It will make the framework big and slow. Review collected by and hosted on G2.com.