[Django]-Django or Ruby-On-Rails?

62đź‘Ť

âś…

My best answer is for you to learn both.

Consider this your end goal, and instead consider your question as, “Which one should I learn first?”

I recommend that you start with Django, especially if you have Python experience. Django’s approach, like that of Python itself, is more condusive to learning. Once you’ve gotten your feet wet, learn Ruby on Rails, because that’s the framework that will net you easier cash when you get out into the modern Web 2.0 workforce.

Once you’re thoroughly familiar with Ruby on Rails and have been working for a bit, continue learning Django. Refamiliarize yourself with the basics, then start to learn some of the more advanced stuff. Django’s inner guts are supposedly easier to dissect than that of Rails. If you ever find yourself faced with a job opening with a surprisingly novel and challenging web platform to implement, you’ll find your Django knowledge quite handy.

Here’s a bulletized rundown:

Django

  • Great documentation
  • Thorough tutorial to ease you in
  • Fewer files to understand at first (vs. scaffolding in Rails)
  • Built on Python, which you might as well know anyway
  • More similar to enterprise stuff like Java Servlets/JSP
  • Easier to dig into its innards

Ruby on Rails

  • It’s what’s hot
  • Hot means more jobs
  • You want money, don’t you?
  • When you want to make a “traditional” web 2.0 site, its generated code lets you get done really fast
  • Integration with JavaScript libraries
  • Built on Ruby, which you might as well know anyway

Verdict: Django first (do the tutorial), then Rails, then Django again

👤Wesley

19đź‘Ť

I’d suggest you to do some research regarding technologies trends and professionals demand, you can do this by using Google tools, such as Google Trends
enter image description here

See more details about technology research here. Happy coding!

9đź‘Ť

If you’re more familiar with Python, then you should do Django. Google App Engine is a big user of Django, and you can use that to “sharpen your saw” in Django skills, for a cost-free investment.

👤C. K. Young

8đź‘Ť

Learn both.

Look for a company, where the people (without ties) have fun working there and speak compassionate about there work. This matters far more, than the technology they’re working with.

👤Andre Bossard

1đź‘Ť

If you are low on time, and have to choose one, just choose the one, for which you know how to program. If you know python, learn django, if you know ruby, learn rails. Both have excellent tutorials, and reference materials, RoR rules in screencasts, django rules documentation and tutorials.
If you have a lot of time on hand, say 3-4 months, then learn both. What’s wrong with that?

👤roopesh

1đź‘Ť

try ruby…I love ruby over python then I prefer rails over django…but if you try ruby and don’t like it your best option would be django…

👤angel

0đź‘Ť

I think it depends on how much convention you are used to. Coming from MVC4 to Django I like alot of things, but find I am writing more code where django calls for configuration vs convention. I have found that there are alot of generic methods that I am finding that reduce this, so it might be a learning curve issue for me.

👤Yablargo

Leave a comment