Well, hopefully more like Go's relationship with Google? The company that pays the bills is their first and most important customer, but as far as I can tell from the outside, the Go team makes its own plans and management doesn't pull rank.

> CF could have kept coasting on what Astro was building, but instead they are paying for it. But in return they get a lot of control.

Supabase pioneered the modern implementation of this model. Probably, RedHat before it? Google also tend to "acquihire" maintainers of popular FOSS projects, like Ben Goodger (Firefox), Scott Remnant (Upstart), Junio Hamano (Git), Guido von Rossum (Python).

The easier/convenient a cloud makes it for a business to use, the more the industry will continue to trend towards lock in

What lock in? They explicitly said:

> Staying open to all was a non-negotiable requirement for both us and for Cloudflare.

They have deployment guides for practically every provider out there: https://docs.astro.build/en/guides/deploy/

And at the end of the day, most of the deployment is just deploying a static site... Which you can do practically anywhere.

No? It's still the same Astro that you can move to any other provider that supports it - and it's just Javascript, so pretty much everyone supports it.

Yes, that's part of the problem, deploying nextjs to cloudflare in the first place used to be an absolute nightmare, let alone the dev experience (I think it's better now)

That doesn't sound too preposterous; I wouldn't assume you'd be able to run a React Router project on Turbopack or Webpack either, and Next.js I think has a way more intricate dependence on the bundler to power a significant chunk of its features.

This is insane to me, and validates my irrational dislike of next.

I have a question. Why can't Whatsapp or Meta make a markdown INFO only website for small business owners (e.g. technicians, shopkeepers, handyman, etc) using their immense reach and clout. The method of using whatsapp groups to keep users updated of the latest updates is not scalable or open.

It does not read like marketing copy to me, what part of talking about draft PRs and framrworks sounds like marketing speak? They're right that CloudFlare having priority access to new Astro features is beneficial for them.

Not sure how to feel about this! I’ve been known to use em dashes every now and then, but I am indeed a fellow human.

I’m close to the vite plugin in particular and have contributed to multiple frameworks around cf integration (simply because I use cf), that’s why I chose it as an example (and it’s one of Astro 6’s biggest features)

What a bizarre comment. What part of it was "not human" in your opinion?

Why did you expect info about deploying Astro to Cloudflare Pages? It's been supported for a long time already.

"I don't care, it's a stupid question."

A meltdown is a meltdown.

Cloudflare is bound to respect the laws of the countries it operates, and if he disagrees with the process, understandable, that was not the way to express it.

I don’t think so since they are using the worker model. My guess is that the first class support will go to that. Though they can do lockin differently (kv, queues, etc..)