3 ms·
> I know this is a kind of shitty riposte but if you don't like the code-base or some feature it is open-source you know I'm aware. Which is why we've develope
by girvo 12y ago
> I know this is a kind of shitty riposte but if you don't like the code-base or some feature it is open-source you know
I'm aware. Which is why we've developed many in-house and open-source plugins, and the like. But, fixing Wordpress' API and developer interface is impossible.
To do so, would require breaking backwards compatibility (or building a compatibility layer, that still won't be 100% due to how many plugins do nasty nasty stuff and rely on implicit behaviour) with the ecosystem of plugins; which are the entire point of Wordpress.
So, we've been building a way to wrap Wordpress' back-end in Laravel. To have proper Composer and Packagist and PSR support, to be able to follow proper development practices, hell, to be able to unit test our code properly: these are things that Wordpress makes far more painful in 2014 than they should be.
PHP may have a reputation for being a nasty hacky language, and Wordpress may have contributed a lot to that reputation, but in this day and age we can do better.