I think it's ok that the Django team wants to keep the codebase clean and maintainable. But from an endusers point of view I understand Zinovii's position, too. Sometimes I feel that Django's feature set is very basic and provides only the bare minimum to get started. For real work you have to write your own extensions, such as template tags, first. Though this approach frees the Django development team from maintaining more code, the downside is, that this approach shifts the burden to the enduser of Django. Now the enduser has to maintain his own code. And it's not only one enduser, but a lot of endusers, each one maintaining its own version. As an enduser, how focuses on getting a site ready-to-work, I'd like to have a ready-to-use framework which provides all the tools I need to get my job done. Why to reinvent the wheel everytime?
Still, I do understand the position of the Django development team. But maybe there will be some time after 1.0 to look at the feature set of Django and think about how to enrich the experience for the enduser :-) > Not my opinion. Custom tags are to Django's templating language what > functions are to Python. Would you advice to avoid writing functions > "unless you really need some (function) that you can't live without > and you know what are you doing" ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
