Why I Do NOT Ever Want To Write Yet Another Web Framework

Author: erics, Posted December 30th, 2010 at 4:32:47pm

Any attempt to write yet another web framework would be an utter waste of time and effort. There are some significantly well-developed and well-supported Open-Source frameworks that would make any singular effort moot. Recent project efforts have taught me valuable lessons about trying to roll one’s own system. Much better to rely upon the many person-years of work that each of the below-listed projects represents. No individual or even a small team can possibly hope to develop as robust a framework as what already exists. By the time that effort came to fruition, the market and technologies would have progressed significantly beyond the deliverable.

Here is a comparison of web application frameworks on Wikipedia: http://en.wikipedia.org/wiki/Comparison_of_web_application_frameworks

As you can see, there are MANY choices, both free and commercial. No need to create yet another. I have NO desire to compete in this arena. Let others pursue this objective while I pay my rent.

Instead, I have chosen to use SproutCore as my front-end, and Catalyst as my back-end server.

SproutCore because it is what Apple uses to build the MobileMe system, and I am an Apple fanboy. Unfortunately, not being a JavaScript expert, learning this advanced system is taking me a long time. Interim front-end development for pre-existing client projects has been accomplished using jQuery 1.4.4, replacing Prototype.js and Scriptaculous.

Catalyst because it uses Perl on the back-end, and has complete access to CPAN modules of every variety. Additionally, by using module Catalyst::Engine::FastCGI, Catalyst supports FastCGI right out of the box!

Categories: Rants, Technology Tags: Catalyst, FastCGI, JQuery, OOPerl, perl, SproutCore