Default EmDash size: 483Mb. Default WordPress size: 70Mb. That's progress?
It is in the present AI climate
EmDash – A spiritual successor to WordPress that solves plugin security
511–520 of 558 posts
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#512Serious question: Why is everyone still using JavaScript to AI-code projects? You can vibe-code apps with real languages now. There's no reason to use an interpreted, bloated, weird language anymore. The only reason interpreted languages were a thing was so you could edit a file and re-run it immediately without a compile step. Compiling is now cheap, and you don't have to build expertise in a new language anymore. A…
If you think that's wild just wait until you find out what programming language their AI tool was written in.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#513Earlier quoted context omitted.
[flagged]
That's not why Wordpress won. Every CMS was doing that, and far far better than Wordpress was or is doing even now, two decades later. WordPress had nothing on Joomla. Drupal was even better, but the barrier to entry was higher. The only reason WordPress won was that a template/theming ecosystem developed around it faster than anywhere else.
[dead]
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#514Earlier quoted context omitted.
So it's spiritual successor, not successor.
It doesn't feel connected in spirit at all though. It is in the same category of app though. So there is that. Categorical descendant I'd say.
Correct, "categorical descendant" is actually more precise given how differently they were built.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#515Earlier quoted context omitted.
How do you deploy menu changes from staging to production?
I remember when I looked at Wordpress for the first time, like 15 years ago, and was baffled that a dev/test/prod workflow involved copying filesystem content, database content, and changing URLs that got saved in the database. I couldn't believe what a steaming pile of garbage architecture it was. Fast-forward to last year and I'm asked to look at it again. Surely, I think, in the ensuing time somebody would have re…
> a dev/test/prod workflow involved copying filesystem content, database content, and changing URLs that got saved in the database.
This just sounds like deploying web software. You always have static assets that need to be deployed, the code/binary itself, and database migrations.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#516Played with this for 30 minutes. looks promising, and of course its rough around the edges. im sure you're working on it, but could not figure out how to add section to page.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#517> 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…
I've managed a couple of WordPress installs for friends and family and my experience has largely been the opposite in that there's very little truly dynamic content. Of the dynamic content, the vast majority could just be an API (either home-grown or paid 3rd party SaaS).
The flip side of the dynamic content is that every Wordpress I've ever worked on is a horrifying mountain of plugins managed by the world's worst package manager. Plugin A needs to be updated because it has a vulnerability, which requires plugin B to be updated, but the theme hasn't gotten updates in 6 years and plugin B is using new stuff the theme doesn't support, so either the site has to be re-built with a new theme or plugin A just needs to be left at a vulnerable version.
Static sites get around some of that because vulnerable plugins only exist at build-time. I'm not worried about using an old version of Hugo or Jekyll, but I'm very worried about using old Wordpress plugins.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#518Earlier quoted context omitted.
[flagged]
That's not why Wordpress won. Every CMS was doing that, and far far better than Wordpress was or is doing even now, two decades later. WordPress had nothing on Joomla. Drupal was even better, but the barrier to entry was higher. The only reason WordPress won was that a template/theming ecosystem developed around it faster than anywhere else.
Your comment is basically agreeing with the parent comment. The free WYSIWYG version of WP was more accessible for laypersons to build their own site and add plugins as they went along. Developers noticed that and started building for WP over other platforms, betting that those layperson-made sites would eventually need features beyond a contact form (appointment scheduling, ecommerce storefronts, sandboxed customer account creation, etc.)
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#519I run a handful of WordPress sites. The plugin problem is real. I've spent more time managing plugin updates, conflicts, and security patches than actually building content for the sites. But the reason I'm still on WordPress isn't loyalty. It's that my clients can maintain their own sites without me. A small business owner updates their own pages, adds blog posts, changes a phone number. No developer needed. That's…
Can't you do that editing with EmDash..?
They could also use Ghost of any other random CMS. Everyone uses WordPress because of network effects in terms of site design and ecosystem. This has been the whole pitch of Squarespace too!
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#520Earlier quoted context omitted.
Wordpress has an amazing talent pool of experienced people. EmDash is starting from zero - but you have to start somewhere! I’m very happy with WP, but I’ll be cheering on EmDash if it gets momentum.
WordPress lost a lot of "experienced people" in the last two years, after Matt Mullenweg decided to wage war on WP Engine.
I really do not know how true that is - or to what extent it matters.