Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare acquires Astro

astro.build

Post reply on HN
Print view View original

201–210 of 409 posts

Re: Cloudflare acquires Astro

#201

Post by solarkraft »

csomar wrote: post #84
philipallstar wrote: post #6

It would be good to understand what Cloudflare gets out of the deal. The article is very much just "Astro, but someone else pays the bills!" which is of course lovely for Astro.

Nextjs doesn’t really work on cloudflare with the latest versions. There is an adapter but it’s buggy as hell. The direction is also likely to continue: https://omarabid.com/nextjs-vercel Source: I use cloudflare and used to run my app there (nextjs) and had to do a migration to vite.js. So the way I see it, this is cloudflare response to vercel.

My god. Every time I touch Next.js in some project I think “hey, this actually doesn’t feel so bad to develop with, dare I say it feels nice?“ and every time I read about it I think “what the hell, this is the worst choice you can make“.

It’s wild that they’re somewhat taking the whole React ecosystem with them.

Re: Cloudflare acquires Astro

#202

Post by jamieatlason »

mpeg wrote: post #72
jtbaker wrote: post #59

Earlier quoted context omitted.

> Nextjs has no support From what I remember, you can't even run a NextJS app through vite?

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)

It's gotten a lot better since last year with OpenNext. Last I tested was Next.js 15 though. Who knows what Vercel has broken with Next.js 16.

https://opennext.js.org/cloudflare

Re: Cloudflare acquires Astro

#203

Post by slfreference »

jjmarr wrote: post #187
mpeg wrote: post #22

Earlier quoted context omitted.

Same reason vercel buys open source... it makes cloudflare always a great deployment option for all Astro sites, which in turn helps cloudflare's core business. For example, Cloudflare released their vite plugin which makes it effortless for frameworks that use the vite env API to run inside workerd (meaning you get to use cloudflare service bindings in dev) back in April and only React Router had support for it. Nex…

I use Astro so I could make my blog a static site and deploy it to Cloudflare pages. I was impressed since I got interactive compilation and state tracking of how many exercises the user completed. https://jjmarr.com/blog/structured-bindings-structs/

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.

Re: Cloudflare acquires Astro

#204

Post by pier25 »

cdrnsf wrote: post #145

I don’t want a framework that’s coupled to a hosting provider.

It's not and will probably never be.

If you want some precedent look at Hono. Initially it was just for the CF Workers runtime (not developed by CF). Then CF started using Hono internally and hired the dev to work on Hono full time. Hono works on any JS runtime.

https://hono.dev/docs/concepts/web-standard

Re: Cloudflare acquires Astro

#205

Post by aatd86 »

efilife wrote: post #181
charleszw wrote: post #76

Earlier quoted context omitted.

I will also say encapsulating everything you just said in a single term, "islands," is a lot simpler and prettier to discuss. At least from my perspective, the naming also makes a lot of sense. Literal islands of interactivity surrounded by an ocean of static.

the naming is backwards then. An island is static, an ocean is not. See how it is a buzzword up to your interpretation?

now that you say it :o

Should be astro lakes or something.

Re: Cloudflare acquires Astro

#206

Post by pier25 »

koakuma-chan wrote: post #9

I am very disappointed with Astro. Who is this framework for? It's been years, and they still don't support unit testing Astro Actions. They still don't support inter-island communication. "Astro v6 is around the corner" - and the only changes are 1. refactored CLI (why? it's perfectly fine) 2. bumped zod to v4 It's great if you want to build a blog or something, but it's definitely far from great for building apps .…

There are tons of options for sharing state between islands.

The docs show how to use nanostores but you can use other libs like vue refs, etc.

https://docs.astro.build/en/recipes/sharing-state-islands/

Re: Cloudflare acquires Astro

#207

Post by woodruffw »

satvikpendem wrote: post #171
woodruffw wrote: post #168

Earlier quoted context omitted.

This is Astro, not Astral. uv is Astral :-) Edit: OP clarified what they meant, I'm sorry for the misunderstanding on my part!

They know, hence why they used e.g., i.e. exempli gratia

I don't think that's really clear. I think we could both defer to the OP clarifying.

For pedantry's sake: neither i.e. nor e.g. would be correct here. You want cf. ("conferatur") to invite a comparison; e.g. is when an example pertains to an instance. In this case uv would not pertain to the instance, because Astro is not Astral.

Re: Cloudflare acquires Astro

#208

Post by mynameisvlad »

cornholio wrote: post #160
mpeg wrote: post #22

Earlier quoted context omitted.

Same reason vercel buys open source... it makes cloudflare always a great deployment option for all Astro sites, which in turn helps cloudflare's core business. For example, Cloudflare released their vite plugin which makes it effortless for frameworks that use the vite env API to run inside workerd (meaning you get to use cloudflare service bindings in dev) back in April and only React Router had support for it. Nex…

So, cloudification: lock the customer into a complex cloud dependent solution they can't easily migrate to some other commodity infrastructure provider.

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.

Re: Cloudflare acquires Astro

#209

Post by 0xFF0123 »

woodruffw wrote: post #207
satvikpendem wrote: post #171

Earlier quoted context omitted.

They know, hence why they used e.g., i.e. exempli gratia

I don't think that's really clear. I think we could both defer to the OP clarifying. For pedantry's sake: neither i.e. nor e.g. would be correct here. You want cf. ("conferatur") to invite a comparison; e.g. is when an example pertains to an instance . In this case uv would not pertain to the instance, because Astro is not Astral.

cf. would invite a fair bit of confusion on an article about cloudflare

Re: Cloudflare acquires Astro

#210

Post by sofixa »

cornholio wrote: post #160
mpeg wrote: post #22

Earlier quoted context omitted.

Same reason vercel buys open source... it makes cloudflare always a great deployment option for all Astro sites, which in turn helps cloudflare's core business. For example, Cloudflare released their vite plugin which makes it effortless for frameworks that use the vite env API to run inside workerd (meaning you get to use cloudflare service bindings in dev) back in April and only React Router had support for it. Nex…

So, cloudification: lock the customer into a complex cloud dependent solution they can't easily migrate to some other commodity infrastructure provider.

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.
Post reply on HN