Why Django as a Web-Framework?
A web-framework is a necessity. There's no point in us writing our own form-handling code and suchlike - instead give up a small amount of control in exchange for having a burden lifted from your shoulders, and never having to write the same code over and over again.
In the case of Django [http://
- Healthy, sensible and transparent development
They have public bugtrackers, mailing lists and such. And seem to know what they be talking 'boot.
- Stable 1.0 Release
It's a vanity thing, but it's good to know.
- Full-Stack Framework
Linus Torvalds is adamant that creating a monolithic kernel [vs a microkernel] was the way to take Linux. Django follows the same principle: they give you a full stack of pieces that work together out of the box to give you a functioning web site. It gives everyone a unique hymnsheet to work from, and the bits are guaranteed to work together and will develop together.
We could use a framework that allows you to choose each segment of the stack from the third-party alternatives, but then we'd enter a world where we'd be chasing the "best" example in each category, and I don't really want to spend my life recreating the system from scratch each time there's a new "better" choice.
- DRY - http://
Don't repeat yourself. Whoops, I just did. Django doesn't.
- It's jazzy.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Pidge Pidge