Live data from Hacker News

EmDash – A spiritual successor to WordPress that solves plugin security

blog.cloudflare.com

71–80 of 558 posts

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

#71

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…

There's always https://textpattern.com/ which is also as old as Wordpress (older?) and better coded. (See also t https://textpattern.org/ ).

It stores plugins as strings in the database, then pulls those strings back and evals them as PHP on requests.

"Better coded" is very much a subjective assessment.

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

#73
post #36

The power of WordPress is not the ease of use, but PHP. Anything built on PHP will be widely used, like Laravel

That used to be a major selling point because hosts enabled PHP for a directory devs would FTP things into, but those days are thankfully long gone. I don't think it's any more difficult to host a JS, TS, or anything else, app than it is to host a PHP app today. In fact, PHP is probably more difficult than something like Netlify.

That’s also nice joke! You are all killing it today

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

#74
post #36

The power of WordPress is not the ease of use, but PHP. Anything built on PHP will be widely used, like Laravel

That used to be a major selling point because hosts enabled PHP for a directory devs would FTP things into, but those days are thankfully long gone. I don't think it's any more difficult to host a JS, TS, or anything else, app than it is to host a PHP app today. In fact, PHP is probably more difficult than something like Netlify.

Well, you’re quite fucking wrong there.

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

#76

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…

There might be pie on your face but they stole my line, https://github.com/HatmanStack/kill-wordpress

I think you need to account for the base rate. There's a lot of WordPress plugin vulnerability disclosures because there's a lot of WordPress plugins and there are enough deployments of the plugins to make searching for those vulnerabilities is worthwhile.

That site warns that WordPress plugins can be abandoned, but that's clearly not a WordPress specific issue. Sure some site could use SSG, but that's a different design.

I certainly don't want to claim WordPress security is good, but I'm not sure that site is measuring anything meaningful.

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

#77
> Solving scale-to-zero for WordPress hosting platforms > WordPress is not serverless

Just not accurate. WordPress doesn't prevent this.. It's up to hosting providers to work on their infra so it can run in a serverless fashion.

For example: https://www.agiler.io

That's serverless wordpress that scales to zero.. no changes to WordPress, plugins or anything else.. just platform infra.

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

#80

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.

EmDash with some aggressive caching and SWR is effectively this, and we're getting closer to that every day. When the cost of maintaining the data part of the CMS is effectively free, you're basically working with a static site anyway.

I haven’t used Wordpress for a few years. But with WP Super Cache (1) we also always did pretty much that: On saving a post/page the static HTML would be written to a cache directory and be the default content served to visitors.

[1] https://wordpress.org/plugins/wp-super-cache/

Post reply on HN