Understandable sure, but why bring up Django on a post about upgrading to Rails 6.0 a week after 6.0 was released?

Because I too followed the common advice and started with Django (I only knew Python back then). Well, I hated it and got burnt out as a result. So, despite the conventional wisdom, I decided to change my stack from Django/Python/Celery to Rails/Ruby/Sidekiq and I am very glad I made the leap.

I have seen both sides of it, that's why I decided to vent it out.

P.S. Don't get me wrong, I have tons of respect for people doing open source and don't want to badmouth Django folks. But in my limited experience, it just wasn't a great experience.

This is all fair enough - you're entitled to your opinions developed through your experiences - but it's just not relevant to this article. Just because you got burned by Django does not mean it makes sense to pop into any thread about Rails and talk about how you got burned by Django. That's not what this article is about!

Because Rails and Django are two competing web frameworks which are majorly directly comparable, and it's good to know the pros and cons between each one.

Not everybody is an expert on both, so it's nice to see concrete lists like the one posted above.

Unless there's more you didn't explain, you weren't burned by Django -- at most you were lightly singed by your own expectations. Everything you've described is more a matter of "I liked this one more than that one" -- things that are so minor or inconsequential to the actual hard work in building a SaaS app so as to be rounding errors. On the other hand, you haven't described a single area where feature parity is lacking, so it comes down to a matter of opinion and taste.