On Thu, Apr 28, 2011 at 12:55 PM, Hannes <[email protected]> wrote: > So I was surprised > so see that Pylons is discontinued and is going to be absorbed in > Pyramid.
Actually Pylons has just gone in legacy mode. This means just that instead of having Pylons2.0 (which was intended to be a rewrite of pylons) we will have Pyramid. But Pylons1.0 will continue to exist. It won't get new features, but will be bug-fixed. New features will be demanded to higher levels frameworks that work over pylons, like TG. > And I was even more frustrated when my first impression with > Pyramid was less than satisfactory (Maybe too complicated or poorly > documented for a beginner?). Hence I chosen TG. and so far so good. I > am really enjoying it :) > Personally I got to "hate" Zope (it was the reason that caused me to switch from Python to RoR for web development long time ago) and I have a strange feeling about Pyramid. They technically did an excellent job and It is indeed a really good project but to me it "smells bad", like a dish that I might recognize that it is well made but I really don't like how it tastes :D TG has been the first framework that made my say "woah! This is exactly how a web framework should be!" and so personally I'll be commited to maintaining and improving it for long time. I think that if Pylons someday won't fit TG anymore for any kind of reason we will have to take a decision without breaking compatibility with existing applications, but this will be far away in the future as currently the Pylons team is still maintaining Pylons itself. -- 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.
