On Aug 25, 2:39 am, Iain Duncan <[email protected]> wrote: > Actually, Ben has said exactly that before, thought I can't remember > where, I think maybe his blog? That's the kind of thing I'm just saying > should appear more prominently on the Pylons web site. That said, I > don't think making direct digs on Django is such a great plan, but in > the blog post Ben did a great job of pointing out that Pylons has been > popular for people who have prototyped large apps on Django or Rails and > were looking for the long term foundation.
I wouldn't make a dig on Django at all. It's just that Django/Rails let you build a certain , structured kind of app. They're amazing not just to prototype in, but stellar at putting things into production and growing quite significantly. But at some point in time, frameworks stop helping and start hurting. Instead of making you do things faster, they're restraining you and making you code around things , have includes you don't want and hurt performance, etc. I've come to that point in a Pylons app myself -- SqlAlchemy has become too much of a hassle for anything other than some basic add/ edit on records, and I'm migrating all of my pages to use custom data structures that can be cached and manipulated better. Pylons, and even SA, are pretty awesome in being able to let me do that sort of stuff. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
