WordPress Is in Trouble

Original Article ↗ Hacker News Discussion ↗

Scale and role of WordPress

  • Commenters cite numbers like ~44–40% of websites using WordPress and ~79% of web using PHP.
  • Many note that WordPress powers everything from tiny blogs to large news sites, largely because it’s cheap, ubiquitous, and accessible to non-technical users.
  • The massive plugin/theme ecosystem and availability of freelancers are seen as core moats.

Current conflict and governance concerns

  • Thread centers on the dispute between Automattic/WordPress leadership and WP Engine, including lawsuits, blocking access to wordpress.org infrastructure, and trademark/API issues.
  • A major flashpoint: Automattic cutting sponsored WordPress core contributions from ~4,000 hours/week to ~45 to “match” WP Engine’s contributions.
  • Many worry that a single individual effectively controls wordpress.org infrastructure, user accounts, and project direction, creating a dangerous single point of failure.

Forking vs staying

  • Some predict or advocate a major fork once a credible group or sponsor (e.g., a large company or major host) steps up and provides governance and plugin-compatibility.
  • Others argue inertia, existing plugins, and user ignorance of the drama mean WordPress itself will likely persist; a fork may fragment rather than replace it.
  • Concern that without a canonical fork, plugin compatibility and critical mass become messy.

Alternatives and migration experiences

  • Many report moving or planning to move away: Hugo, Zola, Jekyll, Astro, Pelican, Grav, Kirby, Statamic, MediaWiki, Dokuwiki, ProcessWire, Strapi, Ghost, Craft, Publii, various wikis and static-site–plus-CMS setups.
  • Multiple first-person reports of relatively painless migrations to Hugo or other SSGs for blogs/portfolios, sometimes with export tools.
  • Others note most nontechnical users will not manage git/Markdown/CI; WordPress.com, Squarespace, Shopify, Wix, etc. still win on ease and integrated plugins/e‑commerce.

Static sites vs dynamic CMS

  • Strong enthusiasm for static sites: simpler, cheaper hosting (GitHub Pages, Cloudflare Pages, S3), smaller attack surface, easy backups via git.
  • Counterpoint: static sites can still be hacked via server or account compromise; they’re safer but not “unhackable.”
  • Critics note static setups don’t solve comments, forms, forums, or e‑commerce without third-party services (iframes, external SaaS, comment systems like isso).

Technical and architectural debates

  • Multiple comments argue PHP’s ubiquity and cheap shared hosting (LAMP, mod_php/FastCGI) are why WordPress succeeded; no other language currently matches that deployment simplicity.
  • Some wish for a “spiritual successor” to WordPress, possibly in Rust/other stacks, but others argue ecosystem timing and PHP hosting are the real moat.
  • Comparisons to Drupal: Drupal’s backward-incompatible jump from 7 to 8 is cited as a cautionary tale; WordPress’s strict backward compatibility is valued despite architectural messiness.

Security, reliability, and operations

  • Longstanding concerns: WordPress core plus a “wild west” plugin/theme ecosystem creates large attack surface; many mention hacked sites and SEO spam.
  • Some use WordPress purely as an authoring tool and then statically export to avoid runtime PHP exposure.
  • Hosted WordPress.com or specialized managed hosts are seen as safer than self-hosted installs for non-technical orgs.

Open-source economics and “freeloading”

  • One camp sympathizes with Automattic: claims they’ve invested huge engineering effort (thousands of hours/week) in core while commercial hosts profit, contribute relatively little, and even sue.
  • Another camp counters that open-source inherently allows others to profit; WordPress exists at its scale only because of unpaid community work and permissive licensing.
  • Debate over who is “rent-seeking”: some accuse commercial hosts of extracting value from community; others argue using legal and infrastructure leverage against competitors fits that label better.

Leadership behavior and mental health speculation

  • Many commenters describe recent leadership behavior as erratic, petty, or vindictive (account deactivations, public feuds, doxxing allegations, odd UI stunts like the “pineapple on pizza” checkbox).
  • There is speculation about burnout, personality issues, drugs, or investor pressure; others push back that armchair diagnosis is inappropriate and that this may simply be a deliberate, if poorly executed, power/play-for-profit strategy.
  • Net effect: trust in project governance is eroding; agencies and businesses depending heavily on WordPress are reassessing risk and contingency plans.