7 comments

  • ramon1561 hour ago
    Embarrassingly badly generated article, with no real takeaway other than &quot;I let an LLM dig into the code, here&#x27;s what words it chose to describe EmDash&quot;.<p>&gt; Joost put it well:<p>&gt; It’s not a CMS with AI features bolted on. It’s a CMS where AI agents are first-class builders.<p>Joost asked ChatGPT what he should say about the CMS, and you felt like it was a good quote.<p>&gt; Why I won’t use it<p>&gt; I migrated to Astro partly to get away from the CMS.<p>Well then you never needed a CMS in the first place? I also don&#x27;t need use a CMS for my site, but I still maintain a CMS for customers because they do need it.<p>&gt; Does it solve the right problem?<p>This is the only thing I cared about from this article, and the answer is [bag of words]. Are people really this desperate to put their names on new tech? Is it an &quot;I want to be included!&quot; mindset that gets people to prompt an hour of their life away?<p>&gt; Astro itself wasn’t an obvious success from day one.<p>Astro is just the framework they built on, what does this sentence have to do with EmDash? I&#x27;m so confused about what this article is trying to tell me.<p>Also, how come you did not write anything about what it was like when WordPress had just released? I&#x27;m sure there are enough people who can help out with that. Did it have competitors? I wouldn&#x27;t know, I was eating sand when it came out.
    • steve_adams_861 hour ago
      To say Astro wasn&#x27;t a success from day one is a truism. No JavaScript frameworks have been an obvious success from day one. How could they be? Even very well-designed and innovative frameworks and libraries struggle to gain adoption in such a crowded space where tooling as significant as a framework has major inertia. It really is a bunch of words.
  • leetrout1 hour ago
    It&#x27;s on the front page right now below this link but just for anyone looking later:<p>EmDash – A spiritual successor to WordPress that solves plugin security<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47602832">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47602832</a>
  • givan1 hour ago
    I&#x27;m developing Vvveb CMS and WordPress is very inspiring, the standard to which everyone compares in the industry.<p>One of the reason WordPress is so ubiquitous is that it&#x27;s very easy to host and it doesn&#x27;t need advanced technical knowledge.<p>PHP hosting is very cheap and WordPress installation is very easy, it&#x27;s just one click in some hosting dashboards.<p>The Javascript ecosystem is complex, you need to be a developer and have access to command line to install most Javascript CMSes and need a vps or more expensive hosting.
    • cloudpeaklabs1 hour ago
      The hosting story is WordPress&#x27;s biggest moat and most JS CMS projects underestimate it. Though I&#x27;d argue the gap is narrowing - a Node app on a $5 VPS with PM2 is getting close to shared PHP hosting simplicity, and platforms like Railway and Fly have made deploys nearly painless. The real remaining barrier is that non-technical users can&#x27;t self-manage a Node process the way they manage WordPress through cPanel.
      • patates1 hour ago
        What people also underestimate is the new power of the index.php that comes from the LLMs.<p>Tell claude to create a php backend to your portfolio html template, drag the generated file to the cheapest server, and you already have a custom CMS.
  • katsura1 hour ago
    Neither the &quot;Cloudflare’s own announcement&quot; nor the &quot;Joost’s take&quot; links point to the right URL, should be lower case.
    • palmiak46 minutes ago
      Thanks. I realized I was writing &quot;emdash&quot; and when I fixed it, I fixed a bit too much.
  • ramdevsingh55 minutes ago
    the agent access part is what i&#x27;m watching. i&#x27;ve been building agents to write content for my own projects, and the hard part is giving them guardrails. curious how
  • Jeffrin-dev2 hours ago
    [dead]