5 ms·

Bottle vs Flask, who will win?

jsprinkles 14y ago
Why must there be a winner?
ch0wn 14y ago
I hope they will continue to coexist. Competition is great. I personally prefer Flask, mostly because I built my own little framework on top of Werkzeug before and know the code quite well. Also, I'm not a huge fan of the single-file approach, but this is just my personal preference.
- pearkes 14y ago
  How big do your projects get (by LoC) in a single file in Flask? Have you ever looked into blueprints[1]? [1] http://flask.pocoo.org/docs/blueprints/ http://flask.pocoo.org/docs/blueprints/
  - ch0wn 14y ago
    Sorry, I wasn't clear about this. I meant the single-file approach of Bottle.
jessejmc 14y ago
Bottle supports Python 3 (as does CherryPy, Pyramid, and Tornado), while Flask currently doesn't. Depending on project requirements, this may or may not be important.
- jsprinkles 14y ago
  Werkzeug must support Python 3 before Flask can, and Armin has discussed Python 3 support here on HN before (and there's now a FAQ about it).
srik 14y ago
I love he fact that we have so many options. I myself am writing a small event driven web framework and should be out by the end of summer.
DasIch 14y ago
Bottle is older than Flask still the latter is far more popular, has more features, is better documented and has a bigger community. It is really not a question of who will win but who has won.
Marwy 14y ago
I feel like Flask is node.js of python web frameworks. I guess some people just like shiny/new/popular things.
vph 14y ago
Flask has a bigger dev team, but Bottle is a nicer, more elegant micro-framework. From what I can see, the design of Flask can be broken down into 2 phases. The first phase is essentially like bottle. The second phase added class views and the likes. And it became inelegant and verbose. If bottle has something like Flask's Blueprint, which facilitates the management of larger projects, bottle will clearly win as a micro-framework. In the end, who is the winner really boils down to how much love a framework is given to by its founder. Web.py started a generation of nice frameworks, but I think the person behind it didn't put a lot of effort in pushing it forward, and eventually, it just stopped progressing.

Why must there be a winner?

ch0wn 14y ago

I hope they will continue to coexist. Competition is great. I personally prefer Flask, mostly because I built my own little framework on top of Werkzeug before and know the code quite well. Also, I'm not a huge fan of the single-file approach, but this is just my personal preference.

pearkes 14y ago
How big do your projects get (by LoC) in a single file in Flask? Have you ever looked into blueprints[1]? [1] http://flask.pocoo.org/docs/blueprints/ http://flask.pocoo.org/docs/blueprints/
- ch0wn 14y ago
  Sorry, I wasn't clear about this. I meant the single-file approach of Bottle.

jessejmc 14y ago

Bottle supports Python 3 (as does CherryPy, Pyramid, and Tornado), while Flask currently doesn't. Depending on project requirements, this may or may not be important.

jsprinkles 14y ago
Werkzeug must support Python 3 before Flask can, and Armin has discussed Python 3 support here on HN before (and there's now a FAQ about it).

srik 14y ago

I love he fact that we have so many options. I myself am writing a small event driven web framework and should be out by the end of summer.

DasIch 14y ago

Bottle is older than Flask still the latter is far more popular, has more features, is better documented and has a bigger community. It is really not a question of who will win but who has won.

Marwy 14y ago

I feel like Flask is node.js of python web frameworks. I guess some people just like shiny/new/popular things.

vph 14y ago

Flask has a bigger dev team, but Bottle is a nicer, more elegant micro-framework. From what I can see, the design of Flask can be broken down into 2 phases. The first phase is essentially like bottle. The second phase added class views and the likes. And it became inelegant and verbose. If bottle has something like Flask's Blueprint, which facilitates the management of larger projects, bottle will clearly win as a micro-framework. In the end, who is the winner really boils down to how much love a framework is given to by its founder. Web.py started a generation of nice frameworks, but I think the person behind it didn't put a lot of effort in pushing it forward, and eventually, it just stopped progressing.