Posted
by
timothyon Thursday September 04, 2008 @11:18PM
from the by-djove-they've-done-it dept.

jgomo3 writes "Finally, the stable version 1.0 of Django (one of the most popular free Python based frameworks) has been released. Explained in the project blog, this achievement was in part due to the great users and developers community of the Django project, and recall the big effort with numbers like 4000 commits and 2000 bugs fixed since last stable version. Django is 'The Web framework for perfectionists with deadlines.' You can dive in by reading the overview."

...just give it a try. Most people who haven't written any Python think it's an awful idea. Most people who spend a few hours learning Python change their mind. It's just one of those cases where first impressions are totally wrong.

excuse me, i hate to break it to you people but we programmers dont decide what goes on to being popular.

I don't think so. Things are not popular for no reason. Usually, things that become popular have some obvious advantage to existing technology, and that's why people chose it. Only later it is discovered there are also disadvantages to the new technology (usually because it's not so mature in other areas), and even later, the new technology is integrated with the technologies that existed before. It's a natural cycle of progress.

PHP is nice example. It had advantage in allowing having business logic directly in HTML pages (i.e. easy creation of dynamic pages compared to CGI), and was free. But there was a disadvantage to this approach, so the MVC model and frameworks using templates were invented. So the modern frameworks combine advantages of both technologies.

The same could be said about Rails. They use obscure language (sorry), but the basic ideas are sound. That's why they are copied by other frameworks, which combine advantage of more well-known language with the advantages of Rails.

The one really great thing about Django is that it's consistent. There is usually one way of doing things, instead of a million different ways that apply in different situations.

Consistence is good, but why it "one way of doing things" good in any sense? It's not a good thing in all scientific or artistic disciplines I can think of. There are multiple ways to heal all parts of the body and resolve medical issues, multiple ways to perform the same scientific experiments, multiple ways to build a bridge - why do you want "one way" to do something when it comes to developing software? That sounds like a code style dictatorship..