But the trade-off isn't usually worth it.

The time you save initially you'll later spend fighting the framework or debugging its internals.

Python's "explicit over implicit" scales a lot better, especially with large teams.

(personal opionion of someone maintaining production-critical Django and Rails applications)

It was worth it in the case of Airbnb, Twitter, Teespring, Coinbase and many, many others. Once you find product market fit, you can afford to rewrite your entire backend if needed. If you don't win round one, then it doesn't matter how well your stack could have scaled.

FWIW I've never had these issues with Rails, though it does make sense that this would be more common with Rails than most things.

FYI, I just downvoted you but for your edit, not your original comment. Perfectly legit, valid comments get downvoted here for bullshit reasons sometimes, I just ignore it and move on. (FWIW, I've never used Django. I'm not a developer.)

My only concern for karma is as a way to gain insight regarding the opinions of the community and how broken it is.

The parent comment being flagged to death is enlightening on both counts. I also appreciate your telling me you'd comment and vote on a thread about a Django release even though you've never used it and aren't a developer. That's simply fascinating!