On Fri, Dec 19, 2008 at 4:58 PM, Chris B - JK at asciiking dot com <[email protected]> wrote: > > I'm putting together a development site. The first step includes a > placeholder page that describes the tools that will be used and/or > available on the site. I plan to use TurboGears 2 for the the site > meta-content while waiting for a certain killer CMS to come available, > after which TG2 will remain as a wrapper for session management and to > model deployment recipes for WSGI apps. How I describe TurboGears in > the placeholder page will probably be carried forward to the > production site. This is the Draft: > > TurboGears 2 is a web framework for Python that provides the MVC > programming pattern with sane development defaults that is, in my > opinion, more suitable for small enterprises than Django. This is not > to say that TG2 is more or less appropriate for large scale projects > than Django or other frameworks, only that Django is a little fuzzy on > how well it scales down to the individual developer level while > TurboGears more clearly supports individuals and smaller teams within > its model. >
This is interesting, I have heard this argument several times but I haven't heard a good explanation why, could you elaborate (here not on your site) on why django django doesn't works for smalls teams? t o be honest I think it is the opposite, django scales really nice to small groups and things get weird when the group gets bigger, now this is a totally separate item from the questions does TG scales right? I believe both frameworks work really well for small teams (1-5) and I think TG works better for bigger teams, although that is something I do not like to do (more people = more kaos). As for why TG over django, that is really your decision. If I where writing the page I'll say, because SA is the best ORM out there, you get a lot of flexibility, and the framework (or the templates) doesn't gets on your way, and the people are friendlier here ;) > This is the context: > > http://www.kolonelpanic.org/ > > It's important to me to not only accurately describe the tools I plan > to use for the site and/or make available to the users, but to do so > in a way that is satisfying to those who are developing those tools. > Hopefully it will be good marketing for the components, something that > involves not only good opinions but an accurate description that is > consistent with the message that the developers will be promoting. > > Specifically, I want to answer the question "Why didn't you use > Django?" in a manner that is both clear and uncontentious. Since the > site is targeted at individual developers and smaller teams, it makes > sense to emphasize that as the key element of my decision, although my > main concern is ease of integration for deployed components. > > Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
