why did we choose rails over django?

[ruebenramirez]

Today, I was asked why we used rails instead of django.

• I've not worked on as many django apps as I have rails apps, so developer comfort/preference
• totally opinion, but python seems to be a chattier syntax, whereas rails (to me anyways) is less verbose
• ruby = object model all the way down
  • not that you can't write python like this...I think it just wouldn't be very "pythonic"
• package mangement: gems vs pip packages + virtualenv config
  • rails-api gem base -- then decorated it with some more gems and controller logic to tie it all together
  • I'm sure django rest is very capable as well though. I'm not as familiar with the plugins available for django
• scaffolding in rails
  • this was HUGE for the last project I worked on -- we stood up the core of the app incredibly quickly without much config
• [ ] compare and contrast django and rails

[ruebenramirez]

questions about django

• How do the current releases compare feature wise? I'm incredibly outdated on django knowledge.
  • django scaffolding still doesn't seem to exist
• rails console vs python manage.py differences
• rails active record vs django orm differences
• routing config differences
• convention differences
  • rails has a mantra of "convention over configuration"
  • configuration differences -- rails has a config dir with different environment configs -- what does django look like from that perspective?
  • is one easier to leverage environment variable based config than the other? -- https://12factor.net/config