Hi all, I've been away for a while and am trying to come up to speed on some pretty significant developments in the pylons community. I've spent considerable time with the pyramid docs in the last week but have failed to find an answer to one very important question: If your goal (like mine) is to build web apps, what reasons do you have to switch to pyramid?
Let me engage in a bit of flame-fanning here just to make a point. As of right now, pyramid and pylons (v1.0) are, effectively, competing technologies. They are competing for the mindshare amongst Python web application developers. When our BDFLs tell us that pyramid is an improvement over pylons, I believe them but I don't particularly care. As an app-dev, I am pretty much agnostic to things like pylon's extensibility model (http://docs.pylonshq.com/faq/ pylonsproject.html#why-not-just-continue-developing-the-pylons-1-0- code-base). What I care about is how quickly and easily I can get my app up and running, how easy it will be to support and maintain. Bottom line, I think the BDFLs have punted on making a pro-pyramid technical argument to their app-devs, maybe because there isn't one to be made. Flame-fanning finished. And I was lying about not caring. *I BELIEVE* and I want to see pyramid go forward. But in the end app-devs are the least of pyramid's worries; we're always looking for excuses to learn new things. Middle managers are much more difficult to convince. Hence, I'm calling for some management-friendly pro-pyramid propaganda: https://github.com/Pylons/pylonshq/issues/issue/2. If you're an app-dev trying to figure out how you're going to convince your manager to let you learn pyramid, bump it up! Cheers, all! Sorry for the mischief! ~br -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
