Introducing Three Python Web Frameworks (Linux Journal)

I don't see how. He was, in fact, the the first person I had seen advocating Web2Py whose name was not Massimo Di Pierro. And I've been watching reasonable closely. Though admittedly, I did not have a Twitter crawler running specifically to look.

But this is getting silly.

"""
but web2py is very different technically and philosophically
"""

Not really that different. This is the mindset that fragmented the Python landscape so badly that the very arguably inferior Rails, running atop the abysmally slow Ruby, was able to waltz in and absolutely dominate over everything that Python had to offer. Projects felt that some minor difference made it imperative that they go their own way, and so everyone set about reinventing the wheel, over and over and over again in their own garages, dreaming of the day that their framework would one day come into its own as hoards of other people came to realize how wonderful their particular wheel was. And, of course, it never happened for any of them. Unless you count Zope. But that's a whole, sad, story in itself.

I'm being horribly un-PC, of course. The prevailing fashion in the Python web framework community these days does discourage one from criticizing anyone else's framework (unless, of course, one is Mark Ramm). But I am still encouraged by the cullings (e.g. Subway) and consolidation (e.g. TG folding into Pylons) that I have observed during this new generation. Continued insistence that Web2Py is so special that it just has to be yet another fragment on the landscape seems, to me, to be a remaining loose end.