natecox ,
@natecox@programming.dev avatar

I actually worked with Django for years. At one point I was a technical reviewer for the book Two Scoops of Django.

Today I basically refuse to go back to Python (and by extension Django). I am not a fan of the Python community, and I am not a fan of the “configuration over convention” philosophy that Python tends to take.

My experience is that Rails apps are infinitely easier to jump into and understand because convention is enforced at the framework level, and this seems to have influenced the Ruby community in very positive ways. I always seemed to find constructive, useful answers faster from the Ruby community than I ever did from the Python community.

The worse dev job I ever had was doing contracting for Django apps. Every single Django app that was brought to us was configured, architected, organized, and deployed in completely different ways and it made just getting to the actual business logic far too difficult.

Between Ruby/Rails and Python/Django it’s Ruby/Rails all the way.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • wartaberita
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • [email protected]
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • TheResearchGuardian
  • Ask_kbincafe
  • KbinCafe
  • Testmaggi
  • Socialism
  • feritale
  • oklahoma
  • SuperSentai
  • KamenRider
  • All magazines