Django’s Creators Discuss the Framework’s Future
Where does Django go from here? That’s the question that closed out the final talk here at DjangoCon, with the co-creators of Django, Adrian Holovaty (above left) and Jacob Kaplan-Moss, addressing their own ideas for the future of the framework and as well as some “I want a pony” suggestions from the audience.
But before they delved into the nuts and bolts of what we can look forward to, both Kaplan-Moss and Holovaty went to great lengths to stress that Django is still not, at least in their minds, a framework, but rather “a way to get shit done.”
Although it could be taken as quip, after two full days of DjangoCon there’s one thing that’s abundantly clear — the core Django developers are extremely informal and very willing to listen too feedback and criticism. In fact Kaplan-Moss repeatedly stressed the importance of the community remaining open to criticism and admitting mistakes as well as fixing them.
So what can you expect in future version of Django? Kaplan-Moss and Holovaty had a number of suggestions for improving the Django admin — multiple delete, multiple edits and more — as well as support for multiple databases, an updated official Django book and more.
Perhaps the most welcome news (judging by audience response) is that Django will, baring serious community objections, move to a timed release schedule.
Other ideas included bringing the Django community sites together; perhaps using OpenID to handle identity, but also perhaps simply bringing together some of the many community sites — Django Snippets, Django People, Django Plugables, etc — so the sites could share data between themselves.
After outlining their own ideas, the pair turned suggestions over to the crowd, which asked for everything from multiple database support (a running theme at the conference) to ORM improvements, as well as dozens of smaller requests.
[Update: Simon Willison has collected up most of the suggestions and entered them in the Django ticket tracker with the keyword DjangoCon; head over to see a complete list of what the people want.]
The only suggestion that was universally booed was rolling Ajax support into Django. As Holovaty suggested, “that’s what JQuery.com is for.”
And that brings the first ever DjangoCon to a close. But be sure to stop by Webmonkey for all the latest Django news as well as some more tutorials.