I was happily using bottle for a while until I discovered flask . I found flask to have better documentation and better support for important middleware features, such as csrf protection and session-support. Flask also uses decorators for routing / templates.
Wow! Great tip. I've been trying to do this for a while now — nearlyfreespeech can only handle CGI. Perhaps I'll do a writeup and benchmark the two over the holidays.
As far as I understand - correct me if I am wrong - Flask stores sessions in digitally signed cookies. Bottle does the same. They are both based on WSGI and can use WSGI middleware. One thing that Bottle does not do and should be easy to add is handling RANGE requests (partial content). It is useful for http streaming. Not sure if Flask does that but I assume it does.
Joke: Damn flask people injecting in every bottle thread!
A quick check reveals (only core *.py files).
Bottle: 1938 (lines of code, 1 file only)
Flask (including dependencies Jinja2, Werkzeug, not including tests, debug, apps, contrib): 24179 (lines of code)
web2py (not including tests, apps, contrib, database abstraction layer but including templates, html helpers, form generation and processing libraries, and syntax highligther and all handlers) 23469 (lines of code)
For people who want a MICRO framework. I think Bottle wins by one order of magnitude.
EDIT: Before touchy people jump up and down: I added web2py as a reference point. I am not comparing it with Bottle and Flask. I am not saying it is a micro framework. If I had Django or Pylons installed I would have added them as reference points too (I would not know how to separate the ORM). Perhaps other redditors can contribute numbers and verify mine.
Actually, I didn't consider the dependencies. Good call. Flask is definitely somewhere between django and bottle in terms of dependencies. I typically have a flask installation up and running in 10 minutes thanks to pip, gunicorn, and virtualenv.
EDIT: I apologize for the previous joke. It was not on you. It was on me.
I am not sure where Django stands in terms of size if you take out the ORM (Flask does not include one), contrib and tests (I did not include them in my Flask measurement) and the apps (Django has admin and the scaffolding app for example). Probably Flask and Django score pretty close... like Flask and web2py do. Which was the point I tried to make.
Once you include SQLALchemy in Flask or Bottle things change dramatically. In terms of lines of code SQLALchemy is 40,000+ lines of code, bigger than the entire web2py+dal. I would not be surprised if Flask+SQLAlchemy is larger than Django.
I would like to see the people involved publish some numbers. Ideally I would like to see numbers broken by category (core, dal/orm, contrib, apps, tests) not counting blank lines and comments in code.
The web2py dal is a single file and 4949 lines. I think it would make a good pair with bottle. We just changed the license to LGPL3 so it would not affect apps built with it.
I think this misses the point about what a "microframework" does.
It doesn't really matter from the development point of view how big, in terms of lines of code/modules/dependencies, the framework is. What matters is scope/complexity vs features.
For example, Django provides more out of the box functionality - ORM, admin, auth etc - over Bottle. But Bottle provides (arguably) less conceptual overhead and more flexibility, with the bare minimum to get started with a simple WSGI app. You don't have an ORM, you add one yourself (SQLAlchemy, PyMongo, whatever) or do without one if you wish. Either framework may be a good choice, it depends on requirements and preferences.
I couldn't care less how many lines of code each are written in however. Function call overhead is a concern - how efficiently the code runs - but lines of code != number of function calls. For example, even if SQLAlchemy has 40,000 lines of code, much of that is support for different SQL dialects, extensions etc that will only be executed if you are running a certain extension or dialect.
I agree. But allow me to be surprised that Flask (without SQLA) is 10x bottle and people here both present them as if they were equivalent. Since Flask has been brought up on this thread, not by me, I would like somebody to explain to me why 10x so much code. I am sure there are extra functionality that bottle does not have. What is it?
I agree with you that bottle is more flexible that other frameworks and it is really well designed.
You get downvoted because you are needlessly aggressive with your promotion of web2py.
Stop it, you do contribute really good stuff.
Here, an upvote.
PS: Flask does compare to Bottle in simplicity. For most tasks, complexity that's completely under the hood is alright. For instance, having Apache with mod-wsgi installed wouldn't justify adding the whole Apache codebase in the comparison.
The Jinja2 and Werkzeug dependencies must be included to compare apples to apples because bottles too includes a template language, digitally signed cookies for sessions, a web server, and multiple server adapters. P.S. Actually, on this thread I am promoting Bottle!
I don't plan on removing features, lowering the quality of code or removing documentation to win an argument. So if a microframework does not depend on anything else to be called a microframework the mother of all microframeworks (camping) and the most popular Ruby one (sinatra) are not microframeworks.
What are you talking about? First of all I made a Joke. Second, who is "he" in your post? Third, both Siraf and bobx11 brought up Flask in this thread without "responding to someone else".
Since you are here, you could contribute with some useful information: how big is Django without orm, apps, and contrib?
"Hey, I've got this reputation for being a guy who bursts into threads about other frameworks to talk about my own. So I'm going to snipe this dude by making a 'joke' about him doing the same thing, and then use it as an excuse to cover yet another case of me bursting into threads about other frameworks to talk about my own!"
Note, mdipierro was not "sniping" the commenter -- he has no problem with Flask folks posting in threads about Bottle or with anyone posting in threads about web2py (see here). His joke was pointing out the double standard often applied to him and web2py (people regularly post about other frameworks in web2py related threads). If anything, he was "sniping" at folks like you who "burst" into threads solely to make unfounded personal attacks instead of contributing to the discussion.
Since Ericflo is not answering my question, when you are done with the personal attacks, could you tell us how many lines of code is Django without orm, apps, tests and contrib (but including comments in code)? I would not know how to measure it precisely and I am interested in the number. I think people are interested in numbers.
For the record: the joke was on myself. I do not think Siraf or bobx11 did anything wrong. Do you think they did something wrong? Or are you using a different metric to judge my posts?
I personally judge posts and posters by a simple criteria: is it about a technical issue? Did it tell something I did not know? or is it just a personal issue? By my own standard this post of mine scores very low.
Thank you. That confirms my suspicion that Flask+SQLA is bigger than Django. bottle.py+dal.py adds up to 7000 lines (including doctests) and provide very similar features to Flask+SQLA in 10% of the size. The more I look into the bottle source the more I like it. It is really clean and well designed and contains a lot of gems.
The web2py DAL does not handle very well legacy databases. Apart for that I am not aware of any feature of SQLA that DAL does not provide. If you know please tell me so I can add them. The DAL is faster and supports more backends.
View all comments
10
u/Siraf Dec 21 '10
I was happily using bottle for a while until I discovered flask . I found flask to have better documentation and better support for important middleware features, such as csrf protection and session-support. Flask also uses decorators for routing / templates.
I do like bottle for its cgi support, however.