Live data from Hacker News

Cloudflare acquires Astro

astro.build

1–10 of 409 posts

Re: Cloudflare acquires Astro

#2
Astro is amazing. I've been using it for a couple of years now. Initially only for static sites but now I'm building the UI of all my web projects with it.

I wonder if there will be some sort of collab between Hono and Astro given that Yusukue also works at Cloudflare.

Re: Cloudflare acquires Astro

#3
This is cool, I use astro when I just want to spin up a quick site without having to fight the framework (looking at you, Nextjs) and the main thing I disliked was the initiatives around paid extras they had going

Astro and Tanstack are probably the best full-stack routers these days, and Astro wins in terms of the wide support for almost any client-side tech

Re: Cloudflare acquires Astro

#4
Why does Cloudflare need a web framework? Most obvious would be they think they can make money from hosting astro sites (like Vercel and NextJS). I hope Cloudflare's impact on Astro will be tiny. But another great thing being swallowed by big tech...

Re: Cloudflare acquires Astro

#8
post #2

Astro is amazing. I've been using it for a couple of years now. Initially only for static sites but now I'm building the UI of all my web projects with it. I wonder if there will be some sort of collab between Hono and Astro given that Yusukue also works at Cloudflare.

Yup, there's a lot of overlap especially with the HonoX framework that has island architecture as well!

Re: Cloudflare acquires Astro

#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.

Don't know what they are thinking.

Re: Cloudflare acquires Astro

#10
> In 2021, Astro was born out of frustration. The trend at the time was that every website should be architected as an application, and then shipped to the user’s browser to render.

Was it? Hot damn, I knew it'll eventually happen, but we truly are just running around in circles. Eventually these same people will do the same loop around, creating new frameworks because the current "serverclient" model suddenly doesn't make any sense anymore, and of course this should be rendered server-side.

Why are we doomed to repeat this, and why does it happen so quickly particularly in web development? We have each other's histories and knowledge right in front of us, what's missing for us to not continue just running around in circles like this?

Post reply on HN