Hi Oliver -- http://en.wikipedia.org/wiki/FUD :)
Seriously, though... None of your colleagues' statements display any actual investigation of their claims; they're all almost completely wrong. On 5/23/07, OliverMarchand <[EMAIL PROTECTED]> wrote: > a) that's for websites, not serious applications If you can explain the difference between a "website" and a "serious application" I'll be impressed. Django's used for external applications by companies as large as AOL, the Washington Post and Scripps; it's also used within corporate firewalls by Google, AMD, and many others. There's nothing in the tools that dictate how they're used; the level of "seriousness" only comes from the skills of the developers. > b) it will be slow, ORMs are always slow WIthout benchmarks this is a meaningless claim. Yes, there's an overhead, but I'd it's negligible compared to all the other things a system under load needs to do. In practice, the bottleneck in a Django site is the speed of the underlying database (and its IO systems). Take the time you save not having to write and maintain messy SQL queries and spend it tuning your database :) > c) those HTML forms are too limiting I'm not quite sure how to respond to that... This seems to be an argument against web applications in general; Django in no way limits your use of HTML, so if HTML is too limiting for you then stick to desktop apps. ... but learn how to work around the limitations of HTML. Programmers who can't develop web apps aren't going to be very employable in the near future. Good luck selling Django at your company; I hope my answers help. Jacob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
