Jorge Godoy wrote: > Is having choices and having to add a switch to "tg-admin" all that bad?
I think the problem is not whether we are "pro-choice" or not. As far as possible, components should be made replacable. But an important point is that there should be *ONE* "mainstream" choice made for you by the experts (onw way of doing it). From so many postings in this group, I conclude that to be spoilt for choice is one of the main problems of TurboGears (and Python generally, in comparison with Ruby). And this is completly understandable. A big part of the usefulness of a framework is that it makes good choices for you, things you don't need to worry about so that you can concentrate on your actual application. It's all about saving time and getting productive quickly. Being able to make choices is wonderful, but it is also difficult and time-consuming and can leave you with a dim feelign of doubts about your choice. Life is easier if these choices are already made for you. Another aspect is documentation. If you depart from the mainstream choice, you'll be on your own since it will not be covered in the docs (e.g. the TG book) and there will be few other users to help you. -- 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 -~----------~----~----~----~------~----~------~--~---
