you know, back when I first got into Python and wrote Myghty, I got
exposed to this whole "oh no theres TOO MANY WEB FRAMEWORKS" thing
that was going on, which I suppose is still going on, and my casual,
largely uninformed impression of it was that it seemed to be a notion
spearheaded primarily by young, possibly novice developers who were
having a hard time making a decision on how to build their first
dynamic website.
"Suck it up an evaluate them all yourself" is an appealing answer, but not a realistic one. Not when there are, as someone famously pointed out, more web frameworks than there are keywords! If you spent just half an hour evaluating each framework on the python.org wiki, that's a serious time investment.
And experienced developers come from novice developers, so putting up a "novices go away" sign is suicide, from a community POV.
As I've posted before, the ORM space seems to be another area where people seem inclined to create Yet Another Half-assed Project instead of putting forth the effort to contribute to somebody else's project. And that's a shame. Probably because understanding someone else's code _is_ an effort, and perhaps a less-common skill than just starting in coding something solo.
Am I advocating never creating new projects? Of course not. But do I think the bar for "are my requirements really so different that I need to start a new project for them" should be set a lot higher than where most people seem to have theirs calibrated.
--
Jonathan Ellis
http://spyced.blogspot.com