Huh? That's like saying nobody ever writes programs in Python because there are no rules. People don't write their normal apps in frameworks; why are web apps different?
On Feb 20, 2009 9:53 PM, "Hraban Luyat" <[email protected]> wrote: web.py is definitely the framework of choice for the scenario you described: somebody has a clear idea of what he wants to do and he wants to do it right now. Notice, however, that this scenario implies a single individual working on a single project. What if the project is bigger? Multiple people are working on that same thing, different developers on different parts of the system? You can not just let them go around and do whatever they want, web.py style, or it will become a mess. So you set some ground rules, protocol, developers have to talk to each other. You set up a document that outlines certain dos and don'ts of the system and you create some extra hooks here and there that the teams can hook their stuff on to. Lo and behold, you are steadily recreating django. That is what it is for. It is not for a creative individual that wants to go berserk on his newest ground breaking idea, it is for big projects involving many developers who barely know each other. They need some rules, specifications, etcetera. A framework. Luis Gonzalez wrote: > I agree with the comments here about webpy's minimalistic approach and > sim... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
