Cloudflare’s EmDash CMS (https://emdashcms.com/) is an interesting alternative to Wordpress. It’s been built from the ground up using modern technology, and fixes all of Wordpress’ pitfalls - secure plugins, deep AI integration, easy to install, and sensible built-in functionality (like forms). From my initial trials, it looks like it will eat Wordpress’ lunch soon enough.
People can be very religious about their WordPress dedication though, quality alone won’t do it. 
But yes since they promote EmDash for ‘blogs or microsites’ I think WordPress needs to be more worried than ConcreteCMS about it. Because WP is what people use when they don’t want to have to think about anything and just get it running quickly. ConcreteCMS’s ‘selling point’ is more the combination of a user-friendly CMS with a serious development framework that can be used for building specific functionality or even complex web applications.
If people were going to stop using WP just because it’s rubbish it would have died a long time ago!
Most of the clients I speak to still have the idea that they need WP to be able to update content themselves which, alongside familiarity (lots of people don’t want to learn a new system), means I still have to fix it occasionally 
Its not just CMS such as WP that continue on inertia.
Consider the fundamentals behind our much loved Concrete CMS: PHP and MySQL.
PHP started life as a minimal sloppy language and has progressed into being a more fully featured, strongly typed and more precise language with the excitement of back compatibility issues along the way.
An alternate route to more fully featured, precise and strongly typed code would have been to simply switch to one of the many such programming languages that already existed instead of new versions of PHP. We are similarly but more recently limited by the capabilities of MySQL, still moving forward but lagging behind the latest features of other database systems.
Having said that, such continuity considerations are becoming obsolete. I know of a business which used to have multiple Concrete sites that has moved to WP because they could get an AI to do all their site editing and management. The fact that it is WP behind their sites was irrelevant. They don’t need to work with it directly, they just tell an AI what they want. The reason for WP was there was 1000 times as much training data available for the AI.
I do agree about AI, lots of people just want to ask an agent what they want.
That’s why I created REST API: fix roundtrip, export/import IDs by mlocati · Pull Request #13036 · concretecms/concretecms · GitHub (and updated GitHub - concrete5-community/concretecms-mcp-server: A Model Context Protocol (MCP) server that integrates with Concrete CMS's REST API. · GitHub)
The MCP server and easier AI integration are the key to staying relevant. @JohntheFish you’re right that WP has intertia, but as soon as a solution comes along that more easily replaces what came before it, then the old product will decline. Here’s a perfect example:
Stackoverflow: https://www.reddit.com/r/singularity/comments/1q4llh1/stackoverflow_graph_of_questions_asked_per_month/
It has been in sharp decline since 2022 when more people turned to chatGPT and Claude to get programming answers rather than asking in a forum which sometimes took hours or days to get a decent reply (not to mention, risking ridicule from more experienced developers). AI doesn’t (by default) give the same level of pushback which is a drawback. But the ease at getting answers, has made Stackoverflow, sadly, irellevant.
Whoever does this for CMS will win in the end. Making the transition to a new CMS as easy as the original WP “5 minute setup”. One that doesn’t require learning any new concepts or UIs.
As developers, we know that the back-end is important. But end users don’t really care what kind of database or programming language is used. They just want “simple”. Simple and cost effective.