You’re right. But i doubt if WP developers agree with us about changing their framework. There might be some considerations why they won’t change some area of codes. That’s i belive one of the reason why some developers who don’t like this kind of policy start their own blogging software project.

Link:
http://www.brokenkode.com/archives/habari/

I heard that an application with a good design would encapsulate the nitty gritty implementation. So providing WP does have a good design, then they wouldn’t have a problem changing their own framework to other framework without changing their external API (e.g. for plugins).

The fact that Habari Project exists contradicts what you said about WP having a good design.

However, as any other project that was started using PHP4, there are many functionalities that won’t be needed if you use PHP5. And i see they tried to use design pattern on their design, but it gets too complicated when you implement it using PHP4 which is not fully OOP.

But i can understand if they stick to their own framework, instead of switching to others or creating a new one in PHP5. When your software is used by thousands of people, you can’t just change things whenever you like, especially when there are thousands of plugins out there which depend strongly on your API.

Another reason is when your application’s getting bigger and complex, it is hard to change the framework which sits beneath other part of the system. The only possible way to do this is to rewrite the code from scratch.

That’s why a group of developer who’s not happy with the way Wordpress was designed, set up a new blogging platform project called Habari (http://www.habariproject.org) which was written totally from scratch.