Django – What’s the Big Whoop?

I’ve had a little bit of push from my group at work to start learning Python and the Django framework. I’ve been doing PHP for probably over 7 years now and it definitely got the job done for me. Over the past 2 years, I picked up Codeigniter and then the Kohana framework for PHP and it really taught me the point of the MVC (Model-View-Controller) architecture. But ever since I started working at AMD, there’s been a few co-workers who’d been raving about Django for a while and I’d never gotten around to really learning it until now when I’m actually being encouraged to do this next project in Django. It’s like 2:40 in the morning and I’ve been going through it and honestly, I’m not seeing any crazy awesome advantage to using this framework over what I used to be doing with Kohana. I don’t see yet how this is gonna be speeding up my application development at all. Okay, so I’ll give it one advantage: setting up the Models in a file and getting the database to create itself and being able to maintain the database and query it through the ORM is kinda cool. The ORM isn’t really gonna be Django’s selling point for me though because I’m probably gonna end up writing SQL queries myself because they just get too complicated to get an ORM to understand sometimes. One downside is the fact I have to maintain this URL routing file to point HTTP requests to a particular view’s function. It definitely allows for flexibility, but I wish there were some default URL routing that I could follow and only use this URL routing when I want to override the default URL routing. Anyway, I’m just gonna keep on trucking with this Python/Django stuff because I’ve heard good things about Python at least and that’s gonna keep me motivated to keep learning.