Live data from Hacker News

EmDash – A spiritual successor to WordPress that solves plugin security

blog.cloudflare.com

471–480 of 558 posts

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

#471

The Deploy to Cloudflare button in the article is not working for me. It takes me to the expected Cloudflare dashboard page, with title “Clone a repository” and with the GitHub repository URL field filled with https://github.com/emdash-cms/templates/tree/main/blog-cloud... but when I click Continue, the Continue button changes to “…” and animates indicating it’s thinking, but then nothing happens. No error messages s…

Yeah, I had this happen the other day with their Moltworker.

Another one of their products which was “just an experiment”

Cloudflare annoys me as a company.

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

#472
post #427

Earlier quoted context omitted.

It's licensed under MIT. It's more permissive than wordpress.

That is not a pure upgrade, GPL may well be the "better" / safer / trusted /... option for some

You're welcome to take an MIT-licensed project, fork it, and relicense it as GPL. The inverse? not so much.

Hard to sell it as anything but an upgrade if you care about open source.

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

#473

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…

Coded with AI != slop. AI in the hands of the right person can actually be good. That's gotten _especially_ true in the past few months.

Correct. No problem with using AI.

The problem is with letting your AI roam freely to produce hundreds of thousands of lines of code without caring what it produces, which Cloudflare‘s history and the launch post indicate to be the case here.

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

#474
post #265

Earlier quoted context omitted.

Coded with AI != slop. AI in the hands of the right person can actually be good. That's gotten _especially_ true in the past few months.

whether people want to admit it or not, agent encoding is kind of the norm right now and I think the fear is the stories coming out of places like Block, Inc where they announced they fired 4,000 engineers a couple days ago because of what's the obvious truth today versus 6 months ago.... one expert software engineer can do the work of 20-40 people, so why do we need so many people? it's a hard pill to swallow, it's…

No fear. No claim that AI assisted programming is inherently bad.

The indications are that this instance of AI assisted programming is bad because of the launch post, the name, and the history of Claudeflare doing this before.

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

#475

Earlier quoted context omitted.

Huh? That’s not how i think you should be approaching that. I always run local, staging, and production sites. It’s easy to setup and deploy across.

How do you deploy menu changes from staging to production?

Ah. I understand your circumstances better. Short answer - I wouldn’t deploy menu changes. That’s usually low-lift that I would do it manually.

If I was doing it in a recurring basis I would investigate creating a process to export the menu data and import directly using a custom plugin. Or create (via plugin) and endpoint to sync both environments (a bit more work).

I did this one time before for a subset of pages and admin users. There are likely plugins that do this already but you could likely roll your own just for menus in an hour imho.

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

#476
post #183

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 getting so exhausted of the "slop" accusation on new project launches. There are legit criticisms of EmDash in the parent comment that are overshadowed by the implication it was AI coded and, thus, unusable quality. The problem is there's no beating the slop allegation. There's no "proof of work" that can be demonstrated in this comment section that satisfies, which you can see if you just keep following the enti…

I am not implying unusuablilty due to AI involvement.

I am implying that Cloudflare is publishing unusable one-off software without care because they have done it before and the blog post indicates that they are doing it again („look how CHEAP it is to pump out code now“).

I don’t need a proof of work, I need a proof of quality, and the blog post is the opposite of that.

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

#477

> 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 love building static (or statically generated) websites, but all too often, customers want dynamic content. And what's worse, they don't tell you up-front, because they don't really understand the difference. "I need a website for my bakery". "What's supposed to be on it?" "Our address, opening times, a few pictures". I build them a static website. "Now I need a contact form". Ok, that doesn't really fit into a sta…

a friend of mine owns a very popular psych/stoner label

until 3 days ago the website was a bunch of static pages, updated by the "webmaster", no shopping cart, no search, no contact form, just the email on the website

he and his employers have been living out of selling records and band merchandising for more than a decade, before he even created a real company

wanna buy a record? press a button that sends you to the paypal cart

wanna pre order? there is a preorder product on paypal, were you can put your shipping address and when it's ready, it'll be shipped to you

he's been selling in Europe and overseas in the US since the day he started

Now it got to the point where he needed to put different currencies for different regions, taxes, tariffs (UK, USA) so he built a new website that (automatically I guess) show the prices in the local currencies and stuff like that

p.s. still no contact form :)

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

#478

Earlier quoted context omitted.

I love building static (or statically generated) websites, but all too often, customers want dynamic content. And what's worse, they don't tell you up-front, because they don't really understand the difference. "I need a website for my bakery". "What's supposed to be on it?" "Our address, opening times, a few pictures". I build them a static website. "Now I need a contact form". Ok, that doesn't really fit into a sta…

With Astro you can build a static site and if you do want dynamic content later on you can, so you aren't really backed into a corner nowadays.

Built on top of Cloudflare and Workers, I'm assuming this is meant to always build static and use Cloudflare's CDN for "static"

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

#479

Earlier quoted context omitted.

If you have arguments, then make them. This is just saying stuff for the sake of it.

The post literally does that. it talks about how plugin access to core is handled. So to be explicit: if you don't see that as a very significant security improvement over WP's open world, then it may help to understand why. The post also talks about WP ecosystem downside due to this.

  | "network:fetch" // ctx.http is available (host-restricted via allowedHosts)
  | "network:fetch:any" // ctx.http is available (unrestricted outbound —   use for user-configured URLs)
  | "read:content" // ctx.content.get/list available
  | "write:content" // ctx.content.create/update/delete available
  | "read:media" // ctx.media.get/list available
  | "write:media" // ctx.media.getUploadUrl/delete available
  | "read:users" // ctx.users is available
  | "email:send" // ctx.email is available (when a provider is configured)
  | "email:provide" // can register email:deliver exclusive hook (transport provider)
  | "email:intercept" // can register email:beforeSend / email:afterSend hooks
  | "page:inject"; // can register page:fragments hook (inject scripts/styles into pages)
That are the plugin capabilities. I have no clue how it could replace any serious WP plugin. Of course it's secure ;)
Post reply on HN