4 ms·
in an ideal codebase, such as might result from vertical-slice features being added iteratively plus thoughtfully designed features, feature groups and permissi
by diN0bot 16y ago
in an ideal codebase, such as might result from vertical-slice features being added iteratively plus thoughtfully designed features, feature groups and permissions, could a mature product like wordpress not present different levels of simplicity? "enable simple blogging only" v "enable full cms"
I have first hand experience with this and I think it is not only possible, but a reasonable goal for any well designed product. (the advantage of dynamic feature walls is already a huge win)
- jacques_chester 16y agoWordpress, like Microsoft, are bound by the golden anchor of backwards-compatability. One of their big selling points -- the multitude of themes and plugins -- is also what prevents them from making any radical architectural improvements.
- calvin 16y agoThey're dumping PHP4 and MySQL4 support in WordPress 3.2. You're right, they have to consider support for existing themes and plugins, but they're not chained to the past.
- jacques_chester 16y agoThey're going to start using PHP 5 features, but that won't remove the large amount of PHP 4 code they already have. Neither will it remove the vast body of plugins/themes from play, most of which are updated quite sporadically. If there's anything that will cause internal architectural changes, it's the project's general focus on new features over any other goal.