Wordpress is, just as phpBB, old and has a lot of technical debt. The difference with phpBB is that Wordpress gets more developers attention as it powers 40% of all websites. The code is old, outdated, but stable.WordPress is basically the web script's world gold standard, as far as one-click-upgrades go.
This feature alone would propel phpBB into a league of its own, forumwise.
Thanks for considering it!
I like more how Flarum is, codewise: a tiny core and as much as possible functionality in extensions. All is then handled as dependencies by composer. Then it can be easily installed from the command line. And from the admin panel if wanted. That is possible, because composer is written in PHP. This kind of organisation is beneficial to get developers on board and development done; everyone can just focus on an extension. Development becomes less hierarchical and more horizontal. More than 10 years ago it was already suggested in the area51 development forum to chop phpBB into extensions and let everything handle by composer. Though it seems phpBB won't go this direction. That could be because of difficulties of technical debt.
So about this topic 'update phpBB from ACP', I would go more far and say: chop everything in extensions, make composer the centre of all dependency managment (one composer.json at root). Then phpBB can be installed and updated from cli and ACP.
Another thing I think is good about Flarum is the focus on just one database, MySQL/ MariaDB. MySQL/MariaDB is everywhere available and good enough, so why bother bout other databases and introduce complexity in the development? The developer resources are (or have become) limited, so better be optimized.
Statistics: Posted by martti — Sat Jul 13, 2024 7:22 am