Comments on: Notes on a Django Migration

By: shacker

shacker — Wed, 18 Nov 2009 07:57:23 +0000

Thanks Al. I actually have done a fair bit of work on it, though it’s been specific to a project at work. I really need to abstract that work out and back into the distribution. Good to know someone is using it and cares! Thanks, will bump up the priority on that.

By: Al

Al — Wed, 18 Nov 2009 07:41:19 +0000

On django-todo.
It’s a pity you don’t continue working on it…
Well done though

By: shacker

shacker — Wed, 18 Mar 2009 05:34:06 +0000

Kalin – I did my best to account for Django Reinhardt with the “-reinhardt” in the query above, but of course you’re right – google trends cannot possibly be scientific – but it does give you a good sense for things (there’s no other “django” in the lexicon that’s been rising in popularity over the past few years to account for the graph going upwards). But yes, your chart is probably a better representation. The key here is pointing out not which one is more popular (total numbers) but in which direction the lines are moving.

Again, I haven’t used Rails so can’t speak directly, but I sure see and hear of a lot of Rails developers jumping over to try Django and never going back! But that’s just my anecdotal impression from watching Twitter searches for Rails and Django.

By: Kalin Harvey

Kalin Harvey — Wed, 18 Mar 2009 03:32:39 +0000

That’s a bit of a misleading trends graph you’ve got there, since django exists in thousands of searches that don’t include reinhardt or python. Not to mention that it shows a pile of searches in 2004; Django didn’t make it’s first public release until July 2005.

Trends is almost impossible to be scientific with, but this graph is probably a lot closer to reality than the one you put together, other metrics such as number of books published on the subject, or number of conferences would show a similar multiple in terms of Rails popularity.

Nothing against Django of course, I’m a rails developer but am currently considering geoDjango for a maps based project, and from all accounts it’s better out of the box for newspaper publishing.

As for your comments in #13, it’s not correct to call Merb a copy of Django in Ruby, any more than it’s acceptable to dismiss Django because it took some inspiration from Rails. Merb, was an attempt to bring about some component flexibility and more focus on core code that was perceived to be missing in Rails.

And a note to post #12 by Barinder Singh: Drupal scales ok for everything but developer time and patience.

By: shacker

shacker — Wed, 24 Dec 2008 18:24:37 +0000

Barinder – For the reasons noted, we’re not interested in PHP based systems. And Drupal is a CMS, not a framework (you might want to read the article again). Merb is interesting, but looks basically like an attempt to copy Django in Ruby (why not just use Django if that’s what you want?)

By: Barinder Singh

Barinder Singh — Wed, 24 Dec 2008 17:53:09 +0000

Nice post,

Have you looked into Drupal ?…. Its a cms which scales like anything.
Yeah but django is also great…
And rails joining hands with merb for rails 3.0… so scalability problem wouldnt last long in rails also.

By: shacker

shacker — Sun, 07 Dec 2008 16:03:25 +0000

Thanks for the tip on that John. Looking forward to giving it a listen this week.

By: John Tynan

John Tynan — Sun, 07 Dec 2008 15:25:36 +0000

Congratulations! Great to hear this article mentioned in This Week in Django 47.

By: Claus

Claus — Fri, 05 Dec 2008 14:15:49 +0000

Thanks for mentioning the shortcomings of the documentation. I’m in a similiar situation like you. Regularly, I fail to find the right pages or to understand what I am supposed to do to solve my problems. Outdated tutorials all over the web don’t make it easier.

The current Pagination document, on the other hand, is really easy to understand. Thanks a lot!

By: shacker

shacker — Tue, 25 Nov 2008 19:33:53 +0000

@phillc – Thanks for noticing. I’ve re-done the search graph to eliminate results including “Reinhardt” (the result is virtually unchanged).

By: phillc

phillc — Mon, 24 Nov 2008 05:05:41 +0000

Your trends graph includes search results for django the jazz musician

By: Dan

Dan — Sat, 22 Nov 2008 19:42:23 +0000

Very informative and encouraging. I’m starting my own Django project, and it’s good to see others that are succeeding.

I think you hit the nail on the head with :

It’s all about the data model. Get this right and you win.

Taking the time to get the model right is always worth it.

Good luck to you.

By: Milan Andric

Milan Andric — Fri, 21 Nov 2008 17:55:15 +0000

So glad you wrote this Scot! And that you’re having fun with Django. I think it’s incredibly useful for people to get an accurate picture of what is going on in the web dev world. And this post is not just for developers but for anyone poking around trying to get a handle on things. This is immensely useful on multiple fronts, only you bridge these gaps.

The app engine section might have some factual errors. From what I have read about Google App Engine, it does not require Django. So “they released it with just one deployment option: A somewhat modified version of Django” is incorrect. You can write complete applications with GAE without using Django. A limited version of Django is provided in the GAE distribution. The ORM nor the admin will work, that was stripped out. The core of app engine is separate and has nothing to do with Django, but the google gods did bless it in their own way by including it in GAE.

By: John Weaver’s Development Blog » Blog Archive » Django Migration

John Weaver’s Development Blog » Blog Archive » Django Migration — Thu, 20 Nov 2008 18:53:36 +0000

[...] just wanted to point out a great article by Scot Hacker, about his experiences migrating to a Django & Python based platform. My company is in the [...]

By: Lee Hinde

Lee Hinde — Thu, 20 Nov 2008 18:06:15 +0000

You’re exactly right about the use of shell snippets in the docs. Unlike you however, I just whine about it. Thanks for taking the time to update the pagination docs.