They can stay open source, but stop putting any effort into supporting deploying to cloudflare's competitors, including accepting PRs for such improvements.

Or they could add features that only work if you deploy via cloudflare.

I also take anything said in an acquisition announcement with a grain of salt. It is pretty common for companies to make changes they said they wouldn't a few years after an acquisition.

Once again, it’s a static site builder. How, exactly, would they “stop supporting deploying to cloudflare’s competitors”? Be specific.

The same ways Vercel makes it harder to deploy Next.js sites to competitors or for self hosting.

Next.js isn't just a static site generator.

Neither is Astro. Not sure what your point is.

Yes it is. All of the providers support “Static”, which literally means uploading /dist to your provider of choice.

They also have three pages worth of deployment adapters for one line deployment on many platforms, including many built by the community. https://astro.build/integrations/?search=&categories%5B%5D=a...

Did you even bother to look at their site or even better the guides I posted upthread or just decide to pull that out of your ass?

Did YOU even bother to look at their site? They support more than static generation, including SSR and even API endpoints. That means Astro has a server that can run server-side (or serverless) to do more than static site generation, so it's not just a static site generator either.

And yes I can see you're posting the same lie all over the comments here.

Stop being a potty mouth.

Vercel does not make Next.js hard to deploy elsewhere. Next.js runs fine on serverful platforms like Railway, Render, and Heroku. I have run a production Next.js SaaS on Railway for years with no issues.

What Vercel really did was make Next.js work well in serverless environments, which involves a lot of custom infrastructure [0]. Cloudflare wanted that same behavior on CF Workers, but Vercel never open-sourced how they do it, and that is not really their responsibility.

Next.js is not locked to Vercel. The friction shows up when trying to run it in a serverless model without building the same kind of platform Vercel has.

0. https://www.youtube.com/watch?v=sIVL4JMqRfc

So it is vendor locked by Vercel. That's why there is OpenNext - https://opennext.js.org/

How is it vendor locked?

Recent features are more dependent on Vercel and it's OpenNext that makes it platform independent with adapters.

Can you describe what you mean here? Because I have heard this about 100 times and never understood what people mean when they say this. I am hosting a NextJS site without Vercel and I had no special consideration for it.

Yeah. For now.

That's always been true. Perhaps even more so as Astro constantly faced an existential battle for a working business. Now they don't have to do that and Cloudflare makes their money on their infra business. Locking Astro up now or in the future gains them very little compared to how much they make with hosted upsell services. [edit: clarity]

It's a static site builder. It creates a static site. HTML, CSS, and JS. That you can then upload literally anywhere.

Once again, what lock in? There is literally nothing to lock in. Explain exactly how they are going to lock somebody in, moreso than the lazy "for now" which you seem to constantly repeat.

They can say whatever they want, and then do whatever they want. They have no contractual or legal obligation.

Almost every (it seems) acquisition begins with saying, 'nothing will change and the former management will stay on'. A year later, the former managment leaves and things change dramatically.