• Why Django Sucks, Except When It Doesn’t

    by  • 8 June 2012 • Articles

    Ken Reitz is a smart man. Very smart. Smarter than me. He’s responsible for some of the best, most widely-used Python libraries out there. So when he talks, I listen.

    And recently, he talked about why Django sucks.

    Ken made some really excellent points. Among them:

    • Django is too monolithic, and so…
    • it encourages big, tightly-coupled apps.
    • Everything depends on the Django ORM, whether it’s front-end stuff like sessions or back-end stuff like data persistence.
    • Broad knowledge of the system is required.
    • All components get deployed together.

    He also had plenty of nice things to say about Django, but (and Ken, correct me if I’m wrong) the point seemed to be that we should take a page from Steve Yegge’s infamous rant and try to separate concerns (e.g. why do user sessions have anything to do with data persistence?) which means building smaller silos that talk over APIs (maybe HTTP, because it’s easy).

    These silos are easier to understand, can be deployed, scaled, and updated independently, provide more opportunities for fault-tolerance, and have a number of other advantages.

    So why on earth would you just use Django as-is?

    Because for a lot of people, none of that matters.

    If you’re prototyping a new project, or if you’re a start-up and need to ship something, or if you’re just one person working on a little app with a few (even a few tens of thousands) of users, odds are that none of those benefits are worth losing the nice stuff Django gives you, or the time it takes to build APIs (even using existing apps to do it) or abstraction layers between the silos.

    A while ago, someone tweeted something to the effect of “while you were arguing about Rails vs Django vs Flask vs Erlang, a bunch of people shipped with PHP.” That’s my sentiment here. 99% of the time, for 99% of web apps, the benefits of doing things the “right” way are just never going to show up. Start with the easy, fast way.

    Twitter is the perfect example. Today, the website is a web client that talks over APIs to the real messaging service and yadda yadda yadda, but on launch day, it was a Rails app, and, from the outside, it didn’t even seem like a particularly clever Rails app.

    Django (or Rails, or even Flask with some packages from its ecosystem) gives you a lot in the box. Unless you know that you’re launching to millions of users, it’s OK to take that box and start building.

    If you end up in a place and at a scale where that’s technical debt you really need to pay off: congratulations!