No criticism at all, although it would be nice getting the relevant user's benefits of the change. The complexity I talked about as well the allergy to zope is a personal perception I would wish expressing here (perhaps I'm the only one feeling that, then just don't care about it)
I decided to jump from django to pylons beacuse I felt pylons to be open and simple. I enjoyed using it and I wish thanking immensely all the contributors My allergy to the name of zope shall play a role in personal future decisions, whichever portion of it is going to be used here Complexity is measured to my way of thinking from a user perspective, not necessarly from a framework code number of lines developer point of view Regards Daniel On Nov 5, 10:44 am, chrism <chr...@plope.com> wrote: > On Nov 5, 5:34 am, daniel <daniel...@orange.fr> wrote: > > > had a quick look at pyramid ... too complex to me and not really > > understand for which benefits, which could not be handled with the > > lovely pylons .. > > More specific criticism would be helpful. > > > I feel should consider whether it's time for me to step back to > > django .. I always hated zope (useless ?) complexity and I love simple > > way of thinking > > I've spent ten years using Zope. Pyramid is not Zope. It does use > several packages in the zope namespace, but end users never use or > need to care about those packages. They're a framework implementation > detail. > > - C -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
