Live data from Hacker News

EmDash – A spiritual successor to WordPress that solves plugin security

blog.cloudflare.com

191–200 of 558 posts

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

#191

Earlier quoted context omitted.

Agent coded != vibe coded. I don't write code manually anymore, but Im still getting the exact code output that I want.

It's a tough pill for some HNers to swallow, but with a good process, you can vibe-code really good software, and software far more tested, edge-cased, and thoughtful than you would have come up with, especially for software that isn't that one hobby passion project that you love thinking about.

Shhhhh stop telling them! We don’t need more competition :)

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

#192

Earlier quoted context omitted.

Agent coded != vibe coded. I don't write code manually anymore, but Im still getting the exact code output that I want.

It's a tough pill for some HNers to swallow, but with a good process, you can vibe-code really good software, and software far more tested, edge-cased, and thoughtful than you would have come up with, especially for software that isn't that one hobby passion project that you love thinking about.

This, but I think everybody that's awake knows this. I still not a fan of this project regardless, it's polishing a turd.

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

#193

the plugin security problem in WordPress was never really a code quality problem - it was a trust model problem. any developer could publish a plugin and any site owner could install it with one click, with no vetting layer in between. TypeScript and serverless doesn't change that dynamic unless the trust model changes too. curious how EmDash handles third-party plugin permissions at the API boundary.

It runs each sandboxed plugin inside its own dynamic worker, with a separate bridge worker to enforce permissions. The worker only has access to its permitted APIs.

the bridge worker as permission enforcement is a solid pattern - the plugin can't escalate by calling APIs directly, everything goes through the bridge. the edge case I'd be curious about is plugin-to-plugin interaction. if two plugins share state through a permitted API, does the bridge enforce granular enough boundaries there, or does the trust model flatten at that layer?

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

#194
I don't like that they see the main selling point that the license, is not GPL, and that plugins don't have to license it that way either. I understand that not all developers are comfortable with the GPL license, but it allows to the code continue to be open source and that most plugins are open source also

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

#195

Earlier quoted context omitted.

It's a tough pill for some HNers to swallow, but with a good process, you can vibe-code really good software, and software far more tested, edge-cased, and thoughtful than you would have come up with, especially for software that isn't that one hobby passion project that you love thinking about.

vibe coding implies a complete lack of process. The definition is basically YOLO.... https://x.com/karpathy/status/1886192184808149383

My process is just getting claude code to generate a plan file and then rinsing it through codex until it has no more advice left.

I'd consider it vibe-coding if you never read the code/plan.

For example, you could package this up in a bash alias `vibecode "my prompt"` instead of `claude -p "my prompt"` and it surely is still vibe-coding so long as you remain arms length from the plan/code itself.

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

#196

Earlier quoted context omitted.

[flagged]

This crap thinking has to stop, not everything is "hey agent do this" then sit, wait and publish as is. Also this is a Cloudflare official software, do you REALLY think this is 100% vibe coded without human intervention? Come on...

Considering Cloudflare shat out slop in the form of a "complete rewrite of NextJS in one weekend" and proudly put out a blog post (https://blog.cloudflare.com/vinext/) despite how absolutely dogshit it is:

yeah.

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

#197

Earlier quoted context omitted.

Agent coded != vibe coded. I don't write code manually anymore, but Im still getting the exact code output that I want.

It's a tough pill for some HNers to swallow, but with a good process, you can vibe-code really good software, and software far more tested, edge-cased, and thoughtful than you would have come up with, especially for software that isn't that one hobby passion project that you love thinking about.

I mean to be fair, if you are using agents more than likely you are not thinking about aspects of the code as deeply as you would have before. If you write things yourself you spend far more time thinking about every little decision that you're making.

Even for tests, I always thought the real valuable part of it was that it forced you to think about all the different cases, and that just having bunch of green checkboxes if anything was luring developers into a false sense of security

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

#198

Earlier quoted context omitted.

[flagged]

This crap thinking has to stop, not everything is "hey agent do this" then sit, wait and publish as is. Also this is a Cloudflare official software, do you REALLY think this is 100% vibe coded without human intervention? Come on...

After https://news.ycombinator.com/item?id=46781516 ? Yes, one can unfortunately put that into the realm of reality.

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

#200

Earlier quoted context omitted.

It's a tough pill for some HNers to swallow, but with a good process, you can vibe-code really good software, and software far more tested, edge-cased, and thoughtful than you would have come up with, especially for software that isn't that one hobby passion project that you love thinking about.

This, but I think everybody that's awake knows this. I still not a fan of this project regardless, it's polishing a turd.

[deleted]
Post reply on HN