Ilias Lazaridis wrote: > Comparing with other systems, this admin interface is one of the > strongest points of Django. > > Remember that not every user is able to take all the setup barriers.
If Django were an application intended to be used by end-users, then i might buy this argument. But it's not. It's a framework for developers. >From the front page: >>>> Django was designed to handle two challenges: the intensive deadlines of a newsroom and the stringent requirements of the experienced Web developers who wrote it. It lets you build high-performing, elegant Web applications quickly. <<<< Note the phrase "experienced Web developers". If someone can't deal with having to decide which RDBMS to use, and put that in a conf file, then they're hardly a developer. If someone can't find in the documentation how to enable the admin interface, they're not likely a developer. If someone is thrown by the fact that the admin scripts have ".py" at the end, they're certainly not a Python developer, and likely not a developer at all. I'm not saying Django is a perfect framework, not at all, but none of your suggestions do anything to make a developer's job easier, newcomer or otherwise. Instead, they seem more useful to the proverbial "Aunt Tillie", who is manifestly not the target user. -johnnnnnnnnn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
