On Tue, Jul 7, 2009 at 4:36 PM, eric cs <eeri...@gmail.com> wrote: > Awesome guys, I still can't believe..hheheh > I just mention that to a django guys and he called web2py a mini-framework > and django is more feature for big apps. > Do you agree with that?
I don't know - Massimo has had more direct experience w/ django; but I think this is not an easy question: Django has utilites; in places, web2py doesn't need utilities (I once made a joke @ a sprint w/ a django group; about porting a framework they had - I looked over the features, and wrote a bit of a comical tweet: "We looked at porting your featureset ... until we realized all that was builtin to web2py already") I'll also tell this story: working on a large project (not web based, but that's not important) there were 24 developers on the product. We tried to find why it was hard to add a particular new functionality. It took us a year to model the existing system (names were saying one thing in places where they were actually doing another, similar thing, so developer confusion was wide). When we were finished, the "as is" model had 147 distinct system components (each with several modules). When we analyzed which did what, was responsible for what, and what the "natural" information and task flow would be, we restructured the final design to 13 components. All performance issues of the past dissapeared. The "impossible" feature took 2 people 3 hours to design, code, and begin (what turned out to be final) testing on. This is a bit of an extreme story, but the point is "big" is not as important as "fits well". Django and web2py are similar in some important ways. There are also things (e.g. template language, configuration, etc.) which have a subtly but significant difference. I would say, yes, web2py is a mini-framework - in the sense I described about above - about 13 components being the minimal funcational set of relationships that addressed the application domain. I do not think django has more features for big apps (perhaps more plugins available). You can look at http://en.wikipedia.org/wiki/Comparison_of_web_application_frameworks and see no difference of the sort you are asking about. But, really, to decide pick the front runners, and do some significant test development in parallel, and experience the differences - decide yourself! > I am not a Django guy so I don't know but native > orm,scalfolding,migrations,admin, this community...just amazing, I'm just > wondering to do big e-commerce sites like www.taget.com or > www.bestbuy.comisn't web2py enough, or does it need more maturity? > Thanks. Django has had open, trafficked sites like ljworld,com, and there is a commercial news framework built in django. You can also see sites at http://www.djangosites.org/ - be selective, try what you see (as many sites, here or there, may not be significant). I know when I have been shown "I want a site like this" 4 out of 5 times, I can make the sample site crash, burn, do something bad (thankfully - for the client this brings a little more critical set of questoins about design and implementation, and less about underlying framwork - which, of course, must be stable and dependable.... but that is simply necessary, but not sufficient... not the end of your questions...). I'm not sure what the traffic or data statistics are for these sites, but that is a class of use that exceeds ljworld.com surely. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---