I look at TurboGears as glue for a number of well-written/well- supported libraries.
You could do everything yourself direct with pylons, and load formencode, and some widget library and other libraries that you need, but, the TG2 framework (and presumably TG1) pulls those modules in and for better or worse, their dependencies. What you end up with is a framework that is more a collection of working parts that may not be as optimized as hand picking everything, but, it is infinitely more maintainable because they are able to pull in libraries without having to apply patches each time. Because they don't maintain a fork of the library they include, updates to external libraries are much more easily imported into the framework. That tradeoff consumes more ram and causes instantiation delays in some configurations. What you do run into is the inability to run a small TG2 application on a 'small' 128mb xen/kvm/virtuozzo instance as your environment needs a little more ram to run effectively. It isn't as much an issue on xen as they support unused cpu/ram a little differently, but, it does limit hosting options when looking for a virtualized installation. Then again, you run into the same issue if you use Django, Catalyst or Mason. On May 27, 5:47 pm, AF <[email protected]> wrote: > Out of curiosity, why ARE all these modules loaded? > > At what point is the decision being made? > > (i.e. "I might decide to use the module later... better load it > now.") --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
