News for hackers. Stuff that matters.
Re:Django vs. Flask for a long-term project by 27182818284 on Wednesday January 22, 2014 @05:16PM (#7105750)

    if you go with django, then in the long term, 
    you will have to replace almost every single component
    of django with something else, the only remaining part 
    will be the url mapper.
That has been exactly my experience with a project and it has eaten a lot of time It is the single reason why I'm abandoning Django. Batteries are included, but they are Double DD batteries when I need AA, AAA, etc, etc.
Re:Django vs. Flask for a long-term project by Spiritus on Wednesday January 22, 2014 @05:51PM (#7105944)
I feel the other way around, granted I've played around with Django more than Flask. But the first thing I do when creating a Flask app is pretty much pip installing a bunch of packages to cover the basic functionality Django already provides like an ORM, forms, admin etc.
Re:Django vs. Flask for a long-term project by 27182818284 on Wednesday January 22, 2014 @06:30PM (#7106120)
For what it is worth, I think Django just needs to be updated in a sense. For example, instead of just form.as_p and form.as_table, they should have form.as_bootstrap which you can do separately anyway, but of course that makes it a separate other thing that I need to reach for.
Re:Django vs. Flask for a long-term project by debrice on Wednesday January 22, 2014 @05:21PM (#7105782)
Same here, the remaining is the URL mapper... which I really dislike BTW.