43% of the top 10 million websites run WordPress. That’s not a typo — it’s the elephant in the room no shiny new CMS wants to acknowledge.
EmDash popped up on my radar last week, trending on GitHub with its bold claim: spiritual successor to WordPress. Built on Astro, all TypeScript, promising the dev dream of static perf with dynamic CMS magic. Sounds great. But I’ve heard this song before — Ghost in 2013, Statamic a few years later, each swearing they’d bury the PHP beast. Spoiler: they didn’t.
Look, WordPress isn’t pretty. It’s a 2003 relic bloated with plugins, security patches, and that eternal battle against spam bots. Developers hate it — or at least the ones who cut their teeth on React and Vercel do. Wrestling Gutenberg feels like debugging a ’90s Perl script while blindfolded.
Why Does WordPress Refuse to Die?
Here’s the cynical truth: money. WordPress isn’t just a CMS; it’s an economy. WooCommerce alone pulls nine figures annually. Yoast SEO? Fat margins on premium upsells. That 60,000-plugin ecosystem? It’s a goldmine for indie devs hawking $49 solutions to desperate site owners.
EmDash? Cute. Zero JS by default via Astro islands, Zod schemas that actually catch your typos before deploy. Content in Markdown files, Git workflows that don’t make you weep. But who’s paying? Early GitHub stars don’t print cash.
And non-devs — marketers, bloggers, that aunt with the bakery site — they love WordPress. Point, click, publish. No npm installs required.
“WordPress powers roughly 40% of the web. You don’t dethrone that by being slightly better. You dethrone it by being fundamentally different in ways that matter.”
Damn right. EmDash is different, sure. TypeScript all the way down, no MySQL cruft. Here’s a peek at their content collection setup — clean, isn’t it?
import { defineCollection, z } from 'astro:content';
const blog = defineCollection({
schema: z.object({
title: z.string(),
pubDate: z.date(),
draft: z.boolean().default(false),
tags: z.array(z.string()).optional(),
}),
});
export const collections = { blog };
Compare to WordPress’s functions.php junk drawer. Night and day.
But tables don’t lie. Let’s stack ‘em up, straight from the pitch:
| Feature | WordPress | EmDash |
|---|---|---|
| Language | PHP | TypeScript |
| Framework | Custom (WP Core) | Astro |
| Performance | Requires caching layers | Static-first, fast by default |
| Plugin ecosystem | 60,000+ plugins | Early-stage, growing |
| Admin UI | Mature (Gutenberg + Classic) | Built-in admin panel |
| Learning curve | Low for content, high for dev | Moderate (need to know Astro) |
| Hosting | Anywhere with PHP/MySQL | Node.js environments |
| Community | Massive | Early but active |
Is EmDash Actually Better for Developers?
If you’re a solo dev or small team obsessed with DX — yes, probably. Hot reloads. Intellisense that doesn’t ghost you. Ship to Vercel/Netlify without a sweat. No more “it works on my local WP but not prod” nightmares.
Performance? Astro’s islands mean interactive bits hydrate on demand — zero bloat for marketing pages. WordPress? Even with caching plugins, you’re one bad query from a crawl.
My unique take, after two decades: this mirrors Netlify CMS’s rise in 2017. Great for Jamstack fans, but it stayed niche because content editors rebelled. Markdown in Git? Fine for code reviews, hell for casual users. EmDash’s admin panel helps, but until it matches Gutenberg’s drag-drop bliss, forget mass adoption.
Auth’s the other gotcha. WordPress bundles it (flaws and all). EmDash? Roll your own. Auth.js is solid but heavy. Lucia’s lightweight — Astro-native even. Or Authon, that hosted upstart with free unlimited users. No MAU gouging like Clerk. Smart move for indies, but self-hosting’s MIA.
Who Makes Money in This Fight?
Follow the dollars, always. Automattic (WP overlords) rakes in $300M+ yearly from hosting, plugins, Jetpack. EmDash? Open-source darling on GitHub, maybe VC whispers later. But Astro’s ecosystem is hot — $10M+ funding last year. If EmDash hooks in, someone wins big.
Prediction: it’ll carve a dev-only niche, like Sanity or Payload. 1% of WP migrants, tops. The rest? They’ll grumble about PHP while paying Bluehost $5/month.
Switching hurts. Export WP content? Messy. Plugins? Rebuild from scratch. Hosting shift to Node? Budget talks. Unless you’re greenfield or hating life on WP, stick put.
But hey, try it. Clone the repo, spin up a demo. Feels fresh. Just don’t bet the farm.
Why Should Developers Care About EmDash?
TypeScript fatigue is real — everyone’s bolting it onto PHP dinosaurs. EmDash says, why bother? Native from day one. If Astro hits escape velocity (it’s close), this CMS rides the wave.
Skeptical? Me too. But in a world of Next.js everywhere, pure PHP feels… quaint. Watch this space. Or don’t — WordPress will still be here tomorrow.
🧬 Related Insights
- Read more: Laptop Return Nightmare: Why RAG Pipelines Crumble in Production
- Read more: 790,000 Downloads a Month: TeamPCP Hijacks CI/CD Pipelines at Scale
Frequently Asked Questions
Will EmDash replace WordPress for my agency? Short answer: unlikely soon. Plugins and ease win for clients; save it for modern stacks.
Is EmDash free and open source? Yes, MIT license on GitHub. Core’s free; watch for premium add-ons down the line.
How do I migrate from WordPress to EmDash? Export XML, parse to Markdown collections. Tricky for custom post types — script it or hire help.
