Malcolm Peralty

This is the final part of a six-part series. [Part 1] made the case for splitting WordPress into Classic and Next. [Part 2] talked about the kernel. [Part 3] talked about the admin and editor. [Part 4] covered performance and security. [Part 5] talked about the plugin economy and the contracts that hold it together.… Read more

This is part 5 of a six-part series. [Part 1] made the case for splitting WordPress into Classic and Next. [Part 2] talked about the kernel. [Part 3] talked about the admin and editor. [Part 4] covered performance and security. This post is about the plugin economy and the contracts that hold it together (or… Read more

This is part 4 of a series on splitting WordPress into two products, Classic and Next. [Part 1] made the case for the split. [Part 2] talked about the kernel. [Part 3] talked about the admin and editor. This post is about performance and security. I’m grouping them together because they share a structural trait.… Read more

This is part 3 of a series. [Part 1] made the case for splitting WordPress into Classic and Next. [Part 2] talked about the kernel underneath. Now I want to talk about what’s happening above the kernel, in the admin and the editor. I want to say something up front because it shapes the entire… Read more

This is part 2 of a series. [Part 1 made the case for splitting WordPress into Classic and Next.] This post gets into the runtime itself. What Classic keeps, and what Next burns down. A quick aside on PSR, since I’m going to use it a lot Before I get into any of this, I… Read more

Every plugin author, agency lead, and host I know has some version of this argument running in their head, and most of them aren’t going to write it down. So I’m writing it down, in public for anyone to push back on or dig deeper into. A bit of background on where I’m coming from.… Read more