Personally, I went from rails to django to rails to django to rails again. I think the main reason I like rails is ruby. Once I understood the rails system and ecosystem, I chose it to be my default option for new apps. One thing that the rails community tends to do is living on the edge. For me that didn't work well. I do care about stability and well tested software. Now I don't mind running on an older rails release as long as it's doing what I want in a way that I like. I also like how rails emphasises on testing and the testing frameworks that are available to it. Testing is not a priority for me, but I do it when I have the time because I know it will save me a lot of trouble eventually.
"less chance of breakages during upgrades" This is one thing I admire that django devs strive to achieve. However, lately I'm finding rails to be more conservative with updates and cares more about backwards compatibility which I like. The most effective thing that made me really like rails was that I taught myself not to care about running the latest version of rails. It's ok to run an old-yet-supported version, which made my life so much easier. All gems run great, the version of rails is well tested and patched over and over again, and the limitations and bugs are usually known and documented online. This is why I think I will not move to rails 4.0 until 4.1 is released, and then move to 4.1 when 4.2 is released and so on. Rails is a huge framework that does a lot of things and it does take time to learn not-so-obvious features and ways that rails works with. But once you get there, rails is a really REALLY hard-to-beat framework, IMHO. PS. One thing that I love about django is how it integrates well with the database and actually uses its features like foreign keys and unique column values, where in rails these things are handled by rails itself and not the database (by default). On Sunday, May 12, 2013 5:12:11 AM UTC+3, Jason Hsu, Android developer wrote: > > I'd like to hear from those of you who have switched from Django to > Rails. I understand the appeal of Django (more straightforward to newbies > and less chance of breakages during upgrades), but what makes you like > Rails better than Django? > > I learned Drupal before learning Rails. A Drupal newbie can get up to > speed much faster than a Rails newbie, but Rails has so many capabilities > that Drupal doesn't have. Rails offers dynamic capability, automated > testing, and the option of using version control (which makes it much > easier to back up a site). > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/0hZL6LNx_MQJ. For more options, visit https://groups.google.com/groups/opt_out.
