I would say that the killer feature is using existing components instead of creating their own. In effect the TG community is actually the TG community plus subsets of CherryPy, SQLObject, MochiKit and Kid. Making these components all work together encourages a kind of loose coupling that makes it easy to bring in others. I am not really sure how easy it is in Rails, but changing the templating system or the ORM in TG is sometimes little more than altering some import statements.
That, to me, is the big advantage. Kevin & co. can concentrate on getting stuff done for TG without worrying (much) about the maintenance of underlying components. Python in general offers some advantages as a web development language. Specifically WSGI adds an entire new level of "cherry-pick existing components"-ability to your projects. The goal is to turn the problem of relative fragmentation of python web frameworks on its head and make it a bonus. For software it is important to concentrate on your project's core competency. In the ideal case you only write the parts that are truly important and bring in libraries for the rest. TG is closer to this ideal than RoR. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
