I use Pylons because I love not having design decisions about my application fixed ahead of time. I like being able to swap out the template language if I want, structure my directories in whatever way makes sense to me, and be free to use another ORM or whatever else makes sense to back my model.
I've previously used Symfony, Rails and Django and I always found that a) a lot of things were provided that I didn't need, and in some case these things interfered with my use case or required extra effort to circumvent, and b) in general, some decision had been made by a dev that went against the way I work.
Pylons is basically glue code bringing together a bunch of independent packages providing different pieces of a functional web app. To me, this approach works well, as the framework code is lightweight and stays out of my way.
3 comments
[ 5.1 ms ] story [ 18.2 ms ] threadI use Pylons because I love not having design decisions about my application fixed ahead of time. I like being able to swap out the template language if I want, structure my directories in whatever way makes sense to me, and be free to use another ORM or whatever else makes sense to back my model.
I've previously used Symfony, Rails and Django and I always found that a) a lot of things were provided that I didn't need, and in some case these things interfered with my use case or required extra effort to circumvent, and b) in general, some decision had been made by a dev that went against the way I work.
Pylons is basically glue code bringing together a bunch of independent packages providing different pieces of a functional web app. To me, this approach works well, as the framework code is lightweight and stays out of my way.