I agree with basically everything in that post. Models are too tightly tied to their admin representation. It is too hard to use another ORM with django's contrib apps, and fairly pointless to use one if you can't do that. The admin app itself could benefit greatly from another rewrite, to simplify and open it up. The template language is fantastic for designers and less so for programmers. Enforcing the loading of settings at import time is ... not a choice I would have made, let's just say.
But most if not all of those problems are fixable. Django is just at the beginning of its life as an open source project. It's good enough for serious, professional work now and it's getting better all the time. I think it's going to keep getting better as it attracts more users with more good ideas -- so long as the core developers' bandwidth holds up. :) JP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
