Comments on: Popularizing Django — Or Reusable apps considered harmful.

By: website strategy Adelaide

website strategy Adelaide — Sat, 30 Jan 2010 05:57:43 +0000

make it easy,because if not you will be a harmful less..

By: chiguy

chiguy — Sun, 07 Jun 2009 22:46:09 +0000

Doesn’t easy_install handle dependencies?

By: Frank Malina

Frank Malina — Thu, 21 Aug 2008 14:31:19 +0000

Why the heck do you want to popularize Django? I don’t want anyone else to know about it

By: Coming soon - Django 1.0 !!! « Clueless !!!

Coming soon - Django 1.0 !!! « Clueless !!! — Fri, 13 Jun 2008 06:29:45 +0000

[...] has always been a debate ( read this blog post on popularising Django from 42topics) about the one killer application or a set of reusable [...]

By: Marinho Brandão

Marinho Brandão — Fri, 16 May 2008 21:07:48 +0000

Hello,

with the same worry as you, I was thinking in the last weeks about how to make Django easiest for new users and for maintaining with no worry with remote access.

2 days ago I started the project django-dynamic in the Django Code with the goal to implement all maintenance tasks in a Admin-based application, when you will can set install applications, controls SVN/GIT integration and managing files in the project.

for a while, I am using the little time I have to put in some functions I have already made for project I work on. But in the next weeks I will make all those functions I told.

I think that so, we will have a powerfull tool, util for new users and practical for all.

By: Popularising Django - Part 2 — The 42 Topics Blog

Popularising Django - Part 2 — The 42 Topics Blog — Mon, 12 May 2008 07:03:23 +0000

[...] you would have read my Popularizing Django post, you might know that I consider building a killer packaged app to be the best way to [...]

By: shabda

shabda — Wed, 07 May 2008 08:08:47 +0000

Joshua: I guess python eggs can make that possible.

Jeff: Do you WANT django to be a Wordpress killer?

We don't want Django to be a Wordpress killer. But we sure want an application written with Django to be Wordpress killer.

By: Jeff Eaton

Jeff Eaton — Wed, 07 May 2008 04:09:58 +0000

You're onto something important, I think. In the Drupal community we face a similar problem. It's definitely a more focused tool than Django, with its out-of-box CMS trappings and emphasis on multi-contributor content-driven community sites. But the heavy emphasis on mix-and-match site building with reusable modules (similar to django's applications, if I understand them correctly) means that there are very few "turnkey" solutions built on it.

The real question, I think, is this: Do you WANT django to be a Wordpress killer? The amount of work that goes into polishing a toolkit for use-case-specific mom-n-pop use is considerable. I'm not sure that the payoff is there in a lot of cases.

By: Joshua Mostafa

Joshua Mostafa — Wed, 07 May 2008 04:08:29 +0000

I am totally ignorant of the Django world and almost as ignorant of Python in general. So this might be an ignorant question but ...

Would it not be possible to have some kind of ports repository for Django apps, where applications can register themselves and their dependencies ... then have a simple one-line command that pulls in all said dependencies to install the hypothetical Djangopress? Like FreeBSD ports.

By: Doug Napoleone

Doug Napoleone — Tue, 06 May 2008 19:23:09 +0000

I take your point about how we should make things easier for the end users to install, but pluggable apps are the wrong level.

I think the comparison between wordpress and a theoretical django blogging application is a bit apples and oranges in this regard. A better comparison would be a theoretical blogging package which an easy install just like wordpress and with its own plugin system. Plugins != pluggable apps. Do not make that mistake.

Wordpress with a custom skin and 5 plugins gotten out of SVN would be closer to the mark, but still well off.

Someone tomorrow could come up with a django based Blog system in svn (using svn:externals for all the dependencies) and come up with a custom plugin system like the one WordPress has (plugins are VERY different from pluggable apps, but that is a big discussion).

If you look at some of the larger system developed on top of django you will find something closer to the WordPress way of doing things. Projects like satchmo or my own PyCon-Tech. PyCon-Tech consists of about 12 pluggable apps but you only need one svn install to get it up and running (thanks to svn:externals which brings in everything including the proper version of django its self!)

The apache problem is real, but will change with time. We used to have this same problem with PHP, pre-modphp times. modwsgi is almost ready for large scale consumer hosting. Once that happens (and thanks to Google App Engine I believe that time is much sooner than I previously though) we will start to see Django (and TurboGears, and Pylons) superframeworks emerging.