Live data from Hacker News

EmDash – A spiritual successor to WordPress that solves plugin security

blog.cloudflare.com

161–170 of 558 posts

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#161

I mean it's cool your created a new CMS and all, but beyond the look of the admin interface and publishing flow, I don't see how this is a "Spirtual Successor" to WordPress at all. Its a CMS, designed from scratch, for a serverless world. It has a stricter, well defined API that plugins are forced to use instead of directly calling/overriding core functionality like in WP. But that benefit comes with a CMS that's bui…

> Its a CMS, designed from scratch…

Maybe not scratch scratch: "And under the hood, EmDash is powered by Astro…"

> It's built on top of, and seems to perfer you use CF proprietary capabilities (D1 Databases, R2 for image/media storage, their workers for running things.

D1 is SQLite, R2 is S3, and there are other ways to securely run plugins. If it was designed to only be possible to deploy on Cloudflare, they didn't do a very good job.

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#163

Earlier quoted context omitted.

I'm the main engineer on this. I've also been on the Astro core team for two years, so I do think I understand real open source software and community. As the post implies, I did use a lot of agent time on this, but this isn't a vibe-coded weekend project. I've been working full time on this since mid-January.

[flagged]

how long should it take to gain your confidence? how did you arrive at your number?

the state of the art of software engineering is to use AI. it's just reality

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#164

> Our name for this new CMS is EmDash. We think of it as the spiritual successor to WordPress. It’s written entirely in TypeScript. It is serverless, but you can run it on your own hardware or any platform you choose. Plugins are securely sandboxed and can run in their own isolate, via Dynamic Workers, solving the fundamental security problem with the WordPress plugin architecture. And under the hood, EmDash is power…

I am confused - what are the good “websites” roots? Server-side rendered or not?

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#165

Earlier quoted context omitted.

I'm the main engineer on this. I've also been on the Astro core team for two years, so I do think I understand real open source software and community. As the post implies, I did use a lot of agent time on this, but this isn't a vibe-coded weekend project. I've been working full time on this since mid-January.

[flagged]

There's a big difference between the two. If you still think agent-guided development doesnt work well, you need to update your priors

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#166

Earlier quoted context omitted.

I'm the main engineer on this. I've also been on the Astro core team for two years, so I do think I understand real open source software and community. As the post implies, I did use a lot of agent time on this, but this isn't a vibe-coded weekend project. I've been working full time on this since mid-January.

[flagged]

Agent coded != vibe coded.

I don't write code manually anymore, but Im still getting the exact code output that I want.

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#167

Convince me this isn’t vibeslop. If Cloudflare really have radically changed their software development philosophy lately, this would actually be an interesting project, being based on Astro and coming with some APIs for programmatic management. Them being so happy about the „cost of software development“ and not going very deep into ecosystem, community or project management doesn’t convince me that this is going to…

I'm the main engineer on this. I've also been on the Astro core team for two years, so I do think I understand real open source software and community. As the post implies, I did use a lot of agent time on this, but this isn't a vibe-coded weekend project. I've been working full time on this since mid-January.

What does "While EmDash aims to be compatible with WordPress functionality" mean?

Compatible how?

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#168

It looks like I'm in the minority after reading this comments, but I'm quite happy to see this announcement. A "good" standard, free CMS with theming and plugin support without the issues of Wordpress is _welcome_. (And the issues are many: Licensing, trust, drama, security, and cost). I'm guessing that a lot of cynicism here is coming from this crowd not being the target market of Wordpress in the first place? What…

I think the cynicism is related to cloudflares recent previous releases that were considered to be slop that significantly overpromised on its capabilities/completeness. Trust can take a long time to rebuild.

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#169

A WordPress spiritual successor backed by Cloudflare sounds great in theory, but the headline feature, plugin isolation via Dynamic Workers, only works on Cloudflare's runtime. On any other host it's just a TypeScript CMS without the security model that justifies its existence. Open source but architecturally locked in.

> Open source but architecturally locked in. You hit the nail on the head. Cloudflare's new business model is to find popular OSS projects, create a vibe coded alternative that only runs on Cloudflare's infrastructure.

Sadly, it looks more and more like it. It’s sad, because they were doing wonderful stuff.

Re: EmDash – A spiritual successor to WordPress that solves plugin security

#170
post #153

Earlier quoted context omitted.

I'm the main engineer on this. I've also been on the Astro core team for two years, so I do think I understand real open source software and community. As the post implies, I did use a lot of agent time on this, but this isn't a vibe-coded weekend project. I've been working full time on this since mid-January.

I think one of the reasons people think this is slop is because of the name. How does the name EmDash relate to being a wordpress spiritual successor? It's clear the name was chosen as it relates to the use of em dashes in AI generated text, so why would you want to be associated with that? Why not choose a name like Astro Press given your experience on Astro?

> It's clear the name was chosen as it relates to the use of em dashes in AI generated text

this is not clear to me, and is not discussed in the article

you can like or dislike the name. but criticizing the quality of work based on your affinity for the name is foolishness

Post reply on HN