Choosing a Web Development Framework

I recently had the opportunity to develop a small online booking system. This time round I was determined to make use of some development framework. Not for me the slow slog of writing all my code from scratch - surely we have moved beyond that now in web development? The big question was - which framework to use? Since the advent of Ruby on Rails, development frameworks have become quite the flavour d'jour and there are now, well, maybe not thousands of them, but quite a few! The last time I heard there are about 80 development frameworks out there. I am not 100% user of this number, it could be a bit higher, it could be a bit more conservative (on this site you can find about 40 PHP frameworks listed - http://www.phpwact.org/php/mvc_frameworks). The point is, the web developer is now really spoilt for choice. Which is a problem in itself, since having too much choice can leave you dithering between different options. This article is therefore about how I made my choice, which was CakePHP, and which factors I took into consideration. Obviously and certainly I will get bombarded with "Why don't you try X framework, it is really much simpler to use..." type responses. That is quite OK, to each his own! But this is the choice I made and I am sticking to it. Frankly, the idea of going through another learning curve gives me the heeby-jeeby's.... I found that the selection criteria were not independent. In other words, once I've ruled out some frameworks due to some specific criteria, other factors came into play. It was therefore more a process of elimination than judging all the frameworks off a predefined set of criteria. The first major selection point was: Ruby on Rails or not. Obviously there is the attraction of using a brand new, hip, buzz-word hyped framework. You can't go wrong with something that is getting so much attention... or can you? Let's look at some of the selection criteria that filtered out Ruby on Rails" 1. Ease of installation and ability to run on shared hosting The problem is that most of my clients make use of a shared hosting environment. Can Ruby on Rails run on common-or garden variety type shared hosting? The answer was, I soon discovered - no. One needs to either have access your own private servers or run on a shared hosting environment that has Ruby on Rails pre-installed. Admittedly, there are a couple of them now starting up. A comprehensive list of hosting providers that offer Ruby On Rails hosting can be found on the RoR Wiki - http://wiki.rubyonrails.org/rails/pages/RailsWebHosts. 2. Minimize the learning curve Even though I knew that any new framework will involve a steep learning curve, I really didn't have the guts to go through TWO learning curves - one for the language itself and one for the framework. I might still have been prepared to go through the learning curve though if it wasn't for the fact that RoR requires special hosting. So basically the decision was: Not RoR. And based on criterion 2, I decided to stick to a PHP framework, and not go for something else based on Perl or something else since I've been developing in PHP for the past two, almost three years. Having said this, it is all very well to say that CakePHP allows you to use your PHP skills - because it is an object oriented framework/MVC based framework it has its own rich language infrastructure. You still need to learn the CakePHP terminology and the learning curve is pretty steep! 3. Ability to run on PHP 4 Although PHP 5 offers more object oriented features, once again, not all shared hosts offer PHP 5 out of the box. I decided that I wanted to stick to a framework that will offer backwards compatibility and enable me to run on most of the servers that I, as well as my clients, host on. My further criteria came down to: 4. Must have good documentation Under good documentation I count the following: - User manual - Examples and code snippets - Screen casts and videos - although I do not see these as essential 5. Good support by the user community This, in combination with formal documentation is absolutely essential. All of these frameworks are pretty young and the documentation is also constantly evolving. Some documentation might be patchy in details. This is where the user support in terms of the community comes in. How active are the forums? Is there a bug tracker? Any other informal tutorials, write-ups, comments, blogs and other support? 6. Regular upgrades and bug fixes ..but not so close to each other that the software becomes unstable and unusable. Backward compatibility is also important. Version number of the software can be used to indicate maturity. Working off the following list (http://www.phpit.net/article/ten-different-php-frameworks/) one can see that the list has narrowed down to the following frameworks: