[dead]
EmDash – A spiritual successor to WordPress that solves plugin security
491–500 of 558 posts
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#492Earlier 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…
A contact form is a really bad argument for not making the rest of the website static first.
I don't think they disagree? They said that okay, that doesn't perfectly fit into the static site philosophy but he can hack something together. Which is correct.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#493Earlier quoted context omitted.
I have no idea if it’s still true but it used to be the case that you had 3 choices with a Wordpress install and even a couple plugins: 1) Have a part time job updating it and plugins, making sure you weren’t introducing vulns at every step 2) Leave it as is and hope that no vulns are discovered for your particular version or plugin versions 3) Have things auto-update and pray that your plugins don't get sold or comp…
4) Don't use a stack of plugins, if you must use any keep them as dumb as possible and stick to those with a longstanding reputation. A basic instance, set to auto-update, installed on a shared webhost where OS/web server updates are someone else's problem is pretty foolproof. A VPS running a long-term distro set to auto update is almost as good. --- That said I personally dropped Wordpress for static site generation…
Sure, that's possible, but so much of the value of Wordpress is in the plugins.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#494"..aims to be compatible with WordPress functionality"
What does it mean, to be "compatible with functionality"?
At a first glance this statement promises a lot, but does it really mean anything technically?
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#495Earlier quoted context omitted.
yeah it's strange, if you are building a CMS in AI times, I think you would want an llm integration first. Not a UX clone of WordPress. The UX of WP is sort of a historical clutch not a plus.
I'd go the other way. Have less stuff. Just a text box, markdown, insane support for mermaid and everything. Dump the "blocks" of wordpress etc. Too confusing and fiddly. Maybe have AI assist to help with styling the rendered page a bit.
yeah same, but hn is AIfobic, so gets downvoted. So many cool stuff is now possible, LLM with integrated review features etc.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#496Earlier quoted context omitted.
There are great standard CMSes that do everything technically better than Wordpress (not that it's harder to jump higher than a rock, but hey). That's not the hard part. Every developer should build a good CMS once. The hard part is displacing Wordpress market share; building a community of bloggers, marketeers, agencies, web designers, and so on; creating a huge ecosystem of paid and free plugins, allowing plugin de…
> There are great standard CMSes that do everything technically better than Wordpress Like?
CraftCMS for example is a great example of what you can achieve with PHP; there's Directus or Strapi for headless CMS, for example; or Ghost, Contentful, Storyblok and more as SaaS alternatives.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#497Earlier quoted context omitted.
The constant hacks are side effect of Wordpress popularity. Every discovered security flaw is exploited by bots almost immediately. Unless you keep up with the updates you are very vulnerable. It is not because wordpress is built on "legacy" stack. Other CMSes on that stack (and many are very popular) don't have this problem.
I think the security issue is that people trust random plugins without reviewing them. I’ve been running WP with small and large companies and no big security issues. You either build your own plugins or go with the trusted few you need to augment your operation.
This is the way. WordPress's is so popular because you can get it to do or be anything. I have done some terrible terrible things to WordPress. Need a simple blog? No problem! Want a LMS? Sure why not! e-commerce? Go for it! CRM? Absolutely! Etc etc.
But there are many many "WordPress" developers out there that only know how to glue plugins together, so you often end up with plugin soup.
In the hands of someone who actually knows how to code you don't have any issues.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#498> 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…
We already have Astro
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#499I like the where this is going. The plugins are always the biggest threat. The biggest hurdle will be adoption with all other platforms. One reason WP is still the most used is because all other services you'd ever want to integrate with offer some sort of plugin or integration with WP. Also, so many people use it you know there will always be someone to assist if needed.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#500Earlier quoted context omitted.
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.
Wording never stopped a-holes and lawyers from being annoying. The only difference in this case is that Matt is the small fish.