Added 'Why did you write all of Django from scratch' FAQ question
git-svn-id: http://code.djangoproject.com/svn/django/trunk@652 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
fe01b4d939
commit
aa865f3605
17
docs/faq.txt
17
docs/faq.txt
|
@ -126,6 +126,23 @@ developed precisely because we were unhappy with the status quo, so please be
|
||||||
aware that "because <Framework X>" does it is not going to be sufficient reason
|
aware that "because <Framework X>" does it is not going to be sufficient reason
|
||||||
to add a given feature to Django.
|
to add a given feature to Django.
|
||||||
|
|
||||||
|
Why did you write all of Django from scratch, instead of using other Python libraries?
|
||||||
|
--------------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
When Django was originally written a couple of years ago, Adrian and Simon
|
||||||
|
spent quite a bit of time exploring the various Python Web frameworks
|
||||||
|
available.
|
||||||
|
|
||||||
|
In our opinion, none of them were completely up to snuff.
|
||||||
|
|
||||||
|
We're picky. You might even call us perfectionists. (With deadlines.)
|
||||||
|
|
||||||
|
Over time, we stumbled across open-source libraries that did things we'd
|
||||||
|
already implemented. It was reassuring to see other people solving similar
|
||||||
|
problems in similar ways, but it was too late to integrate outside code: We'd
|
||||||
|
already written, tested and implemented our own framework bits in several
|
||||||
|
production settings -- and our own code met our needs delightfully.
|
||||||
|
|
||||||
Do you have any of those nifty "screencast" things?
|
Do you have any of those nifty "screencast" things?
|
||||||
---------------------------------------------------
|
---------------------------------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue