Flask is nice and I am not complaining about it. Yet, if I needed something small where web2py was too much overhead (and it can be I guess), I would go with bottle.py+dal.py. The bottle source code is beautiful and the routing mechanism seems similar to flask.
Massimo On Dec 23, 5:12 pm, Branko Vukelić <stu...@brankovukelic.com> wrote: > 2010/12/23 VP <vtp2...@gmail.com>: > > > People who think that Django/Flask are superior to web2py, and/or > > web2py is deeply flawed, aren't changing their minds. There's no > > point to debate, justify, etc. > > True. > > <Off-topic> > > I've recently tested Flask briefly. I didn't like it's way of routing. > But then I realized something (and Flask docs confirm that as well). > Flask and web2py are not even in the same league. Flask was developed > to handle small stuff, where having routing stuff dispersed around the > code base is acceptable, because the codebase itself tends to be small > in such projects. But that sucks for larger projects. In contrast, > web2py is geared towards far more organized code, and therefore larger > projects. At least to some extent. I'm not sure about globals, but I > don't develop large projects myself, so it's fine for me. > > So I don't even understand how Flask can be compared to web2py at all. > Two different things, with two different design goals. > > </Off-topic> > > -- > Branko Vukelic > > stu...@brankovukelic.comhttp://www.brankovukelic.com/
