On Aug 24, 2:38 am, Iain Duncan <[email protected]> wrote: > Sorry, I totally disagree. The above may be true for Django, or for the > average person purchasing a Mac, but it is expressly *not true* for > Pylons. The Pylons target user is *not* someone looking for > plug-and-play. You may be, that's fine, but if so, you are probably > looking in the wrong place ( Django or Rails would be much better for > that ).
Has anyone thought of marketing Pylons as a way to grow a Django app ? In my experience, Django/Rails... and even ORM stuff like SqlAlchemy are great at getting a project on its feet... and then they're a f'ing nightmare to grow and scale out of their design patterns. That's why I like Pylons. It's so much more lower-level and easier to swap stuff around in. It's also very responsive to quick changes. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
