What is wrong with hello world application if you are testing web application stack?
Choosing framework X over Y doesn't guarantee any success to project. Good thing to know your framework has a limit... that also tells me how effective one or other implemented... I guess it tells that. I have had no idea until recently that django template are sooo slow... other engines do the same... but spent less time. What the cool feature prevent it for rendering it faster? On Thursday, October 4, 2012 5:14:43 PM UTC+3, Stan wrote: > > > > On Thursday, October 4, 2012 9:50:35 AM UTC+2, Moonlight wrote: >> >> I found the following benchmarks recently: >> 1. http://mindref.blogspot.com/2012/09/python-fastest-web-framework.html >> 2. http://mindref.blogspot.com/2012/07/python-fastest-template.html >> >> It is interesting to see the performance boost using pypy. >> > > > I still can't see why people wast so much time in such biased "Hello > world" tests to claim a definitive "X is the fastest Python web Framework." > Are the Hello world applications are strictly the same (sessions, auth > etc) ? > > Anyway, there are so many ways to fail a project and the reason is never > on the pseudo-helloworld benchmark bad results. Database optimization, ORM, > API quality, documentation, libraries, security. > Does your framework allow users to deliver in a limited time ? That is the > true question. > > Stanislas. > > -- 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/-/_GwVvXhySN8J. 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.
