24 ms·
Really 99% of the arguments I hear about WordPress are because of the community of "developers". Don't get me wrong, there are tons of great developers in the c
by pathartl 9y ago
Really 99% of the arguments I hear about WordPress are because of the community of "developers". Don't get me wrong, there are tons of great developers in the community that are actively working on great features for WordPress either in the form of core or plugins. What I'm specifically referring to are content maintainers that know some CSS, use themes like Avada, and know their go-to plugins to make bloated and convoluted, hard-to-maintain sites.
Really I think where WordPress actually lacks is in the API department. The almost non-sensical approach to partially implemented OOP kills any ambition I have to create a site without my own weird abstraction layer I wrote on top of it all.
- kevinyen 9y agoWordpress has built-in REST API, beginning from their 4.7 release. http://v2.wp-api.org/ http://v2.wp-api.org/
- pathartl 9y agoI'm talking about their PHP API
- sethrin 9y agoWhat gave you the impression that WP was object-oriented?
- pathartl 9y agoI guess you're right, it's really not. Some things are broken out into objects (WP_Post, WP_Term, etc) but I'm pretty sure that's only to utilize the PHP object cache
- sethrin 9y agoWP was itself released a little after PHP acquired classes; before that PHP was purely procedural. However, WP was a fork of an older project, and they kept things procedural in order to maintain backwards compatibility with the previous project. One cannot fault them for that decision in that context. However, apparently we are stuck with the consequences for the foreseeable future. On that basis, I wish that Google were not investing any further time and effort into what I sincerely hope can be described as the last popular procedural codebase in existence.