Drupal has been absolute mess for maintenance, backwards compatibility, responsive ness (code/dev wise).
People started flocking more to WP and Drupal docs weren't just up to date as people were moving away.
Nothing will change my mine over Drupal at this point still especiallyin this day and age. Better create one yourself or mod WP.
---
Whatever the post says about it's "light-years ahead" sounds like a tiktok influencer talk.
I completely understand how people got burnt. The move forward was less about bringing users, site builders, and developers along for the journey and more about providing what enterprise needs.
And one of the enterprises that was front and center was Acquia, Dries' organisation that he set up to offer consultancy services based on Drupal.
Having said all that, it is genuinely a very good product now, and one that LLMs are incredibly good at building with.
The high level of documentation, convention over configuration, and the API-driven nature of Drupal lend themselves very well to LLM assistance.
Considering just how awful WordPress is in terms of security, community, cohesion, code quality and maintainability. I think it's a crying shame that Drupal has lost so much goodwill.
I'm not sure what the solution is, but I'd recommend anyone reading gives it a try with Codex or Claude code, and you'll hopefully see what I mean.
Drupal needs to market how well it can people make $ or at least save. ROI is a good KPI to bring up, if the team has data to back it up, etc.
Saying that Drupal is better than it has ever been is not much of a statement. It still isnt as easily extensible due to having a smaller community of contributors as an after effect of mismanagement.
I hope they have improved, but their reputation has been earned repeatedly.
Easier in terms of effort and time, but it still costs, and it still adds drag.
The fact that I can do housekeeping much more easily with agents doesn’t make me want to do more of it. The whole point is to free up my time, energy, and thinking for things that are more worthwhile, interesting, and value-adding. That’s my mentality both at home and at work.
If you’re building a framework or a library, whether open source or commercial, and you think agentic and AI native development gives you more license for breaking changes and churn because your users can just fix it up with their agents, then I’m afraid I’ve got some bad news for you because that blade cuts on both sides.
If you can keep churning and breaking stuff, then I can get fed up, drop your shit like a hot rock, and build it myself. And I will.
I’ve just rebuilt my personal site from scratch after getting cheesed off with the framework I used and it didn’t take very long. What’s actually taken longer is making all the improvements I would have liked to make but were too much hassle before, so one needs to relearn shipping discipline, but that’s OK.
Same goes at work. Even major stack changes, like migrating database engine, are so much easier. Yes, you still need to be methodical and disciplined - in fact I’d argue agents make that more important than ever in many enterprise contexts - but it is still so much easier. I’m seeing projects left and right that in the old world would have taken weeks or months executed in days or weeks. It’s wild times.
i.e. why read a book written by a human when an agent can write one? Why buy a painting that could have been printed.
One of the benefits of open-source and frameworks is they're made up of battle-tested decisions by a lot of people with real skin in the game for a long time. Yes an agent will often solve your problem, and will solve it correctly - as asked, but often a better answer is found by stepping back, evaluating the fundamentals, checking other perspectives, challenging assumptions, and having an opinion.
I'd rather point the agent at and authentication gem and tell it to use that, vs telling it "build authentication, make no mistakes".