title: Apr 01 2018 - 06:59:23 PM
date: 2018/04/01 18:59:23
slug: 01-065923-pm
status: published
link: https://jj.isgeek.net/2018/04/01-065923-pm/
bookmark_of: {"summary": "Don\u00e2\u0080\u0099t use a Swiss Army knife when you need a power drill\u00e2\u0080\u008a. Wordpress is good for simple websites and fast start.", "title": "Why will Wordpress die | Codementor", "is_image": false, "scrape": false, "url": "https://www.codementor.io/teodeleanu/why-will-wordpress-die-hi97g0q21", "type": "article", "_url": null, "image": "https://cdn.filestackcontent.com/hiqXK1A3QPqV3WTgmjfe", "description": "Don\u00e2\u0080\u0099t use a Swiss Army knife when you need a power drill\u00e2\u0080\u008a. Wordpress is good for simple websites and fast start."}
titleless: True
display_format: entry
syndication: https://twitter.com/jjdelc/status/980520022006222849


Having dealt with Wordpress a handful of times in the past, I can see where is this post coming from.

"Wordpress will die" as in, most sites will eventually graduate out of Wordpress. Many sites start out with it because it's easy to get started, and if the site's needs grow, then WP will quickly tax you a very expensive technical debt. 

All the code written as plug ins is extremely WP specific, has to be PHP (which isn't coolest - personal preference), and the general WP architecture always felt quite unnatural to me. That will make it changing out of WP, an expensive rewrite.

I remember hearing in podcasts, that there is an important rewrite of WP to split the admin and make the backend behave like an API, which sounded great IMO. 

The problem remains when wanting to use WP as the main website engine, I think it's great for a blog that you won't have to touch much, but not for your core site (unless it is a blog).