Hacker News new | ask | show | jobs
by verdverm 73 days ago
> this was top-down, not a skunkworks project

This is telling, though it already seems like it. It's just another vendor's lock-in.

2 comments

That's been the most common criticism, but it already doesn't require CF, and they're explicitly working on extending plugin sandboxing to work on other platforms. Plus, of course, GPL.

I don't see this as any more vendor-locking than a .com account. It's still early days, so can't really judge it as a finished product, but the opening shot across the bow is a big one.

NextJS doesn't require Vercel, but it certainly does not work as well without them. Are wordpress users going to migrate? Who are they targeting with this?

Top-down project directives are a signal the CEO is out of touch and becoming Elon-esc.

As a user, I want a container registry and managed kubernetes. These block my adoption of Cloudflare as a primary provider. This story around emdash tells me to stop considering CF effective immediately. I was already of this mind seeing how little they help developers on Discord and in their own forums.

They're actively trying to avoid any kind of lock in, by the sounds of it. I'm still skeptical myself but it's at least a "wait and see"