Ben on Python Web Framework Niches

Ben Bangert talks about Python Web Framework Niches, specifically detailing TurboGears and Django. I think he’s on the mark that each framework defines its niche based on what it’s asked to do. The best APIs are ones that solve real problems for applications, and not ones that are just created because something sounds neat or potentially useful.

The part that Ben leaves out is the matter of taste (which I touch upon in a comment). I’ve done a lot of work with Perl, and I still think its a good language for quick one-off scripts. Perl certainly can be used to create large systems, and I’ve worked on large systems written in Perl. Some people swear by it, but I don’t like large Perl programs. That’s purely a matter of taste, and I’m sure this extends to the APIs we chose as much as it does to the programming languages we choose.

2 thoughts on “Ben on Python Web Framework Niches”

  1. That’s very true regarding personal taste. I’ve seen people ditch an entire framework because of a variety of personal desires on what they’d prefer. It’s not that difficult (though time-consuming) to create your own framework for Python which is why I’m guessing there’s so many. That, and Python programmers generally are quite picky about using something that meets their personal tastes and requirements rather than just jumping onto an existing framework thats “close enough”.

    I’m not sure what you’re referring to in the way of Perl. Myghty is a pure Python port of Mason (which is Perl). While a large site I was working on in Mason was pretty accomadating, this was mainly because Mason kept a lot of the Perl out of my face. Switching to Myghty was easy, and refreshing as the Perl got ditched in favor of Python. 🙂

  2. Over on your site, I was mistaken saying “Mighty” instead of “Mason”. Here, I’m just making the general point that I greatly prefer Python over Perl for large programs. Perl *can* do large programs, but I find it less fun.

Comments are closed.