Running GitHub on Rails 6.0
My comment on one of the previous discussions:<p>I don&#x27;t want to start a flame war here, but I think Rails (and gem ecosystem in general) is a better choice than Django, at least for SaaS apps.<p>These are all my personal opinions, take it with a grain of salt. Having said that, here we go:<p>* Authentication - it is a pain if you&#x27;d like to deviate from the standard Django User model (using username to login instead of an email). I don&#x27;t like Devise either.<p>* Asset pipeline, even though it is not updated anymore (sprockets) and partially replaced by the webpacker, is still better in Rails<p>* Configuration spread across multiple files, by environment, instead of a single config.py file<p>* Sidekiq has a better API compared to Celery. Also, Celery&#x27;s default broker is RabbitMQ, not Redis. It is really hard to find managed RabbitMQ hosting, for Redis there are plenty<p>* Mailer previews, small but quite useful utility<p>* Better security by default: Rails comes pre-configured with a bunch of security headers[0].<p>* Testing - Minitest and Capybara is just a joy to work with.<p>* I prefer ActiveRecord over Django ORM<p>* Rails isn&#x27;t afraid to deprecate <i>things</i> and move forward. This isn&#x27;t the case with Django, which is big on backwards compatibility. I don&#x27;t like it, since it puts into a disadvantage folks who are starting new projects. Different strokes for different folks, I suppose<p>I could go on and on, but I remember struggling a lot with Django&#x2F;Celery when building a SaaS app. I decided to switch to Rails and haven&#x27;t looked back (Rails has its warts as well). YMMV<p>[0] <a href="https:&#x2F;&#x2F;guides.rubyonrails.org&#x2F;security.html#default-headers" rel="nofollow">https:&#x2F;&#x2F;guides.rubyonrails.org&#x2F;security.html#default-headers</a><p>EDIT: Added last point about backwards compatibility