OliverMarchand napisał(a): > a) that's for websites, not serious applications
All web application programming is about websites. > b) it will be slow, ORMs are always slow Indeed. Plain nothing beats plain SQL in terms of data access, but it may be tedious work to actually write these statements by hand. And Django's ORM is not that bad, if you don't mind fine-tuning your database objects. And, oh, don't forget to employ some memcache. > c) those HTML forms are too limiting True. To get the "feel" of desktop application, one must employ a wide range of hacks. Including hated-by-all javascript. > I have the feeling that all of the above do have some truth ion them, > but weighed against all of the beneficial factors it seems that a > Django solution would overall be a very good idea. As always, it depends. If web application fits your needs, Django will ease the development and make it fun again. But the objections of you colleagues seems to target web applications in general, not the Django by itself. -- Jarek Zgoda "We read Knuth so you don't have to." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
