Django
Sep 14th, 20061 Comment
After messing with Django for approximately 30 minutes, I’m going to write why I immediately took to it over messing with Ruby on Rails for off and on for a few months. This is not scientific, but opinionated. Your views may not be reflected here.
- It’s written in Python, which I know a lot better than Ruby
- You make a web site first, and then applications underneath it. Sounds a lot easier for deployment than an all-over-the-map convention.
- Not only is it written in Python, but it seems to have a Python-mindset in how it arranges things. For example, the model and view for your application are in the same directory (named after your application).
- The tutorial explains
why you want to do something more than any of the Rails tutorials I’ve done. - You can drop to a Python prompt and much around with your site/applications directly. Very cool.
- There is a decent admin that comes out-of-the-box, once you set a few config parameters.
Again, that’s after 30 minutes. But still . . .
