Are web development frameworks still immature ?

February 20 2011, 9:59 AM  by Frosty Z

Just another rant that nobody will read, but at least I will feel better after writing it…

One year has passed since my last post. The so-called Symfony 2 should be released next month, and nothing has changed. Its core team seems, as always, deaf to simplicity and backward compatibility aspects.

Following an interesting comment, I’ve decided to check again Ruby on Rails. Very nice piece of work too, but like Symfony, a very dumb policy for migration between versions. If you want to upgrade a project fromRails 2.3 to the new shining Rails 3, you can choose between spending at least one hour and $9 for an online video, or spending $6 for “Almost 120 pages of upgrade information” (!!??), and obviously, an incredible amount of time for boring and useless rewriting.
At least, unlike Symfony, some people keep migration in mind (if you accept to spend time and money for it), anyway if I were a long-time RoR user, I would feel laughed at.

CakePHP seems to be struck by the same disease. Look what boring stuff you will have to face to migrate from 1.2 to 1.3 minor versions.

That disease has a name : Planned Obsolescence. But I’m not sure that web developers (and their employers) will still blindly follow a such immature and profit-oriented project policy, applied to Open Source web frameworks.

Edit :
– Kohana : painful migrations too… example1(!!) example2
– CodeIgniter : more interesting although not perfect… see this and that.