Comments on: Going for a trot on the Django pony

By: MarkSpizer

MarkSpizer — Mon, 03 May 2010 13:39:43 +0000

great post as usual!

By: Tim Trueman

Tim Trueman — Fri, 26 Mar 2010 17:30:39 +0000

@mike Yes, because Rails originally came up with all of those things…

By: mike

mike — Thu, 25 Mar 2010 07:07:17 +0000

I love how all the stuff you like is a direct ripoff of rails

By: Graham

Graham — Tue, 16 Feb 2010 17:08:21 +0000

Thanks Tim, good overview. Can you (or anyone else) recommend any links for working with Django in TextMate?

By: cyndihugs

cyndihugs — Thu, 11 Feb 2010 06:33:33 +0000

you guys –write– type too much. i think this is awesome…(i really have no clue what you guys are talking about.) I’m going to go get ice-cream. I SCREAM FOR ICE-CREAM!

By: Chris

Chris — Wed, 10 Feb 2010 23:44:12 +0000

The developers of South have asked that it not be included into contrib yet.

It’s currently under very active development and they don’t want the pressure of maintaining backwards compatibility until it’s more mature.

I’m sure that it will be part of django rather soon.

By: Tom Dunham

Tom Dunham — Wed, 10 Feb 2010 16:11:58 +0000

RE: Why isn’t South (or something else) part of Django?

“the developers (both South’s developers and Django’s core team) felt that South would be better served by more time as a separate project where it can develop at its own pace”

– http://jacobian.org/writing/the-power-of-no/

By: Tim Trueman

Tim Trueman — Wed, 10 Feb 2010 06:38:53 +0000

Your point and Simon’s are quite valid. I should have said sharding not split. I think there are some ways Django can support that in the future and it seems they are on the right path. It’s a great time to be using Django!

By: Steve Strutt

Steve Strutt — Wed, 10 Feb 2010 06:16:04 +0000

@Tim: “nobody seems to read this very carefully, what gives”.

My reply was meant to inform you about support in 1.2 if you hadn’t heard about it OR in the interest of clarity for your readers. “Splitting” a database can mean many things. More precise language never hurts.

RE: Sharding though…
Multiple database support creates a nice (reusable) framework for developers to build sharding logic into their apps. The best way to partition a database depends on the app being built. It makes sense to leave this logic up to the developer. It shouldn’t be the job of the framework. Simon Wilson left a good comment about this on another site: http://news.ycombinator.com/item?id=1113307

By: Tim Trueman

Tim Trueman — Wed, 10 Feb 2010 05:52:53 +0000

@everyone (I'm lazy, but thanks for the comments!) Unless I'm missing something from the 1.2 notes it's multiple database support WHICH IS NOT split or sharded database support. Looks like they laid the framework for it in the future though…nobody seems to read this very carefully, what gives? When I say setting up a new project, I don't mean an app. Yes, those are easy. It's setting up a brand new project, changing all the settings, adding in database and media support that takes a while and could probably be more streamlined. Javadocs are alright but what they lack are examples and comments—something that PHP's documentation has down to a science. Don't get me wrong, I like Java, Python and Django documentation too, there's just room for improvement. I'm not sure where PHP stands on performance but the most recent Ruby benchmarks put it ahead of Python. Python is definitely slow by a large margin compared to the vast majority of languages I've worked with but that's something we've just chosen to deal with because programmer cycles are more expensive than CPU cycles. Languages are definitely can definitely differ by more than an order of magnitude on performance and saying no language is slow or fast is just wrong. Tell that to Facebook who just wrote a PHP runtime from scratch for maximum performance. IDE support is pretty lame. I just use TextMate and for now that's good enough (IntelliJ was great, when I didn't see the pinwheel of boredom).