Ask HN: choosing Web framework, again
Just when I was choosing to go with Django for my startup app, I read here that
http://www.mutualinformation.org/2010/03/why-i-switched-to-pylons-after-using-django-for-six-months/
it's not very appropriate when you have more complex sites, etc.
Are there any guidelines for choosing a web framework? I'm language agnostic, but would avoid verbose languages if possible. The framework will be like a bank website, if you want a reference. I want to start web programming but I'm growing more confused every day.
I now heard about Rails, Django, webpy, Grails, Pylons, Lift, Play, Seaside, Ocsigen...
(
5 comments
| 5 points
| on HN
)
That said, I use and recommend Rails. Rails 3 is nearly ready for prime-time and introduces a suite of changes that make it faster, more flexible, and infinitely configurable. The part I have always liked about Ruby and Rails is that even when you are stretching beyond it's intended use-cases, it bends rather than breaks.
That said, Django does have nice admin - you can extend it nicely with Grappelli. Rails ain't too bad itself - here are some variety of Rails Apps (with source) http://jetpackweb.com/blog/2009/10/14/high-quality-ruby-on-r...
Definitely don't pass on Django because of one guy's opinion.
Pylons is a win when:
1. You need SQLAlchemy. 2. You're not really leveraging the Django admin. 3. You don't need anything in pinax or the rest of the django apps.
I actually prefer the various wsgi options over Django (I was a TurboGears committer for a number of years) but Django is better for banging out sites where you need to implement common features since there's a fairly large pool of django apps to draw on. If you're doing something more complex, then there's no real technical (dis)advantage to Django but you'll have an easier time finding people who know the framework and the docs are better.