Live data from Hacker News

EmDash – A spiritual successor to WordPress that solves plugin security

blog.cloudflare.com

61–70 of 558 posts

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

#61

I don't think it's the code that makes WordPress valuable. I've been learning WordPress recently and haven't been too impressed with the internals. WordPress is valuable because of the ecosystem and support. I have no doubt that WordPress will still be a thing in ten years. What's the support plan for EmDash? I see commits are mostly from a single developer. E: Oh, I think it's an April fools joke, I'm embarrassed. E…

Hm, you might want to catch up on the Wordpress “open source” drama with WP.com vs .org, WP engine and Matt.

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

#63

Impressive and created by agents. Another example for skeptics wondering where the AI apps are.

> "Failed to initialize playground" Impressive indeed!

Try again a few times, it ends up loading.

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

#65
post #49

I don't think it's the code that makes WordPress valuable. I've been learning WordPress recently and haven't been too impressed with the internals. WordPress is valuable because of the ecosystem and support. I have no doubt that WordPress will still be a thing in ten years. What's the support plan for EmDash? I see commits are mostly from a single developer. E: Oh, I think it's an April fools joke, I'm embarrassed. E…

Cloudflare doesn't do April fools jokes. In fact, 1.1.1.1 was released on April 1st back in 2018 and now it's one of the most used DNS service in the world.

It's a legit April Fools'.

On the initial commit:

> Some content is hidden

> Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

This for "a spiritual successor to WordPress".

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

#66
post #43
post #13

Earlier quoted context omitted.

> Yes definitely compare it multiple times to WordPress and nobody will think of calling their lawyers. It's not illegal to make product comparisons. That's just competition.

Tell that to the guy who got upset with WP Engine. EmDash is clearly "inspired" by WordPress including in its UI, so there's definitely something to it.

The phrase "spiritual successor to WordPress" is not likely to be judged a trademark violation, though. It doesn't create confusion in the marketplace as to whether Emdash is WordPress.

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

#68

It's a shame they don't seem to try to address the divide between CMS's and static sites. Most WordPress sites could just be static, but WordPress has a nice editor interface, so they're not - unless you use a SSG plugin. Building that into the core workflow (which I believe Astro supports) and giving users a nice hosted editor that produces a static site would be welcome innovation.

The issue with static sites is they can't do comments.

They can - it’s just more complex.

You just put the comments into something like firebase/supabase etc or use one of many off the shelf solutions. Free tier is fine.

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

#70

> 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 think this is true, however, when it comes to non-coding clients I've worked with they really do like the ability to make minor edits to a site with a UI rather than having to continually ping a developer.

The problem with WordPress (and it looks like this solution largely just replicated the problem) is that it's way too cumbersome and bloated.

It really is unlike any modern UI for really any SaaS or software in general.

It's filled with meaningless admin notices, the sidebar is 5 miles long and about 98% of what the user sees is meaningless to them.

Creating a very lightweight, minimal UI for the client to edit exactly what they need or like you said, just static files really is the best solution in most cases. The "page builders" always just turn into a nightmare the clients end up handing over for a dev to "fix" anyways.

Not sure why so many people feel the need to continue on the decades of bloat and cruft WordPress has accumulated, even if it's "modernized."

Post reply on HN