Hi, I won't answer your rheotircal questions ;)
On Thursday, October 11, 2012 8:02:19 AM UTC+2, Yo-Yo Ma wrote: > > BUT... Django is NOT that fast. > We do know that (you know that and probably everyone else too) and I already said in my post that Django isn't the fastest framework out there. The list goes on. What is the harm in discussing the weak points of Django? > Performance is probably the only major weak point in Django right now > (aside from the lack of schema migration in core, which is coming soon > anyway). > There is no harm in discussing weak points in Django, we do it all the time. I just don't think that copy pasting a link (and that more than once) to a benchmark which is (imo) just there as a marketing strategy for another framework (note: I am not saying the benchmarks are a fake, I am just saying they probably aren't representive) adds real value to the discussion. I have no solution or patches in my pocket, but I can say with absolute > certainty that performance will never, ever get better when discourse is in > a monologue format. > I agree to some extend, but I think you shouldn't forget that many core devs use Django on somewhat large-scale deployments (read: definetely way over a blog) and performance issues are fixed as needed. But yes, as you said stuff like templates are probably slower than they should be :/ Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/iVOJwI_v07kJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
