There are some projects that Django is not the right solution for and something like Flask/Werkzeug is definitely better, for sure, but I'm hopeful that the work being done here will help out the majority of people; it brings a lot more than just WebSocket support to the table, that's just the headline feature most people run with.
Flask is basically abandoned, despite continually receiving undocumented commits.
Flask hasn't even had a PyPi release, or even a Git tag for that matter, since June, 2013. The documentation is also far behind.
The other main difference is Django is developed as part of a large organization, Flask is not. Get the right people together and that could be fixed easily...
I use Werkzeug directly rather than Flask, so I can't speak to whether Flask is abandonware or not, but I'm very happy with Werkzeug. With very little effort, I get to build just enough framework for my application, without having to be shoehorned into someone else's tradeoffs.
Have you tried out Falcon, btw? If so, how does it compare to Werkzeug?
They add tons. There are many commits, bug fixes, etc. It's just that there A) hasn't been a release to PyPi, B) is an inordinate quantity of unmerged pull requests, C) are many undocumented changes, and D) issues like https://github.com/mitsuhiko/flask/issues/1272 that are over a year old (I left a comment https://github.com/mitsuhiko/flask/issues/1575#issuecomment-... explaining the vicious circle that I believe is created by not releasing to PyPi). I commit to Django (and donate), but I would never commit to Flask when it makes no attempt at Industry Standards™ like PyPi releases.
I shouldn't have said it's "abandoned", because that's an insult to the parts of the community that are very active.
Im wondering what's a suitable alternative.... with SQLAlchemy and Celery/RQ integration?
On the other hand this feels a bit like "Build the web applications of today, tomorrow!" I think that's an inherent problem with kitchen sink frameworks; new things that come along have be shoehorned into the old way of doing things, except when they can't, and then you have to restructure your foundation. I stopped using Django a couple years ago because the kind of apps I wanted to build were REST APIs, websockets, a little static file serving, and connections to realtime backends like redis pubsubs or RabbitMQ. Django wasn't great at any of those, yet carried a lot of baggage from stuff I didn't need (e.g. form handing, templates).
I would recommend Flask and/or its underlying Werkzeug library (my personal preference) over Django.