Live data from Hacker News

Cloudflare acquires Astro

astro.build

61–70 of 409 posts

Re: Cloudflare acquires Astro

#61

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

    > They still don't support inter-island communication
Can't you just use standard DOM events for that on the client? This would work even pushing events from React to Vue to Vanilla.

Re: Cloudflare acquires Astro

#63
post #32

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

This is overly cynical without reason. CloudFlare is hardly "big tech" even if it is a "big" "tech" company. They have no record of killing or abusing open source projects.

> CloudFlare is hardly "big tech"

yeah, it's still losing money

Re: Cloudflare acquires Astro

#64
post #45

Earlier quoted context omitted.

I havent had a chance to fully use it in a project yet, but it is one of my favorite projects only tinker with it, I'm glad it will receive funding to keep it going. It is definitely a solid gem of open source since its not married to one single SPA framework.

Yeah I suppose it's a tradeoff. I have had an excellent experience when not hydrating components at all, and I like their approach significantly more than other SSGs overall. My worry is just the massive scope of supporting integrations with all those frameworks AND its own .astro language / syntax AND server side rendering in addition to static generation.

To be fair, vite does a lot of the heavy lifting when it comes to supporting extra frameworks. If you look at the code required for astro to integrate with a new technology you'll see it's relatively straightforward.

For example, here's all the code in the svelte integration: https://github.com/withastro/astro/tree/main/packages/integr...

Re: Cloudflare acquires Astro

#65
post #57

[flagged]

> Linux: 33 years old, runs the internet, community-funded Only in dreams, it took off thanks to the likes of IBM that decided it was a way to save costs on their UNIX development efforts, many key projects have been founded thanks to Red-Hat Enterprise licenses, nowadays also part of IBM. GCC, clang, GNOME, Linux kernel, systemd, CUPS, AMD/NVidia drivers, have plenty of big corp money. From https://en.wikipedia.org/…

Big corp money is not VC money. That's the point.

Re: Cloudflare acquires Astro

#66
post #48

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

On inter-island communication, I actually think less is more – I find a lot of the recent big features like this they have added unnecessarily constrain you to doing things a certain way, while the reason I liked Astro in the first place was the simplicity. You can easily add any global store library to your project to communicate between islands from the very simple (nanostores) to more complex stuff (are people sti…

Astro component is your page's entry point. It's similar to React server component. The typical flow is to fetch data in it, and pass the data to client component written in React or whatever. You can also have pages that are Astro only, without any front-end framework.

Re: Cloudflare acquires Astro

#67
post #28

Damn. What alternatives does HN recommend?

Eleventy, of course :-) But why are you looking for alternatives already?

Dropped eleventy recently.

Disliked the templating solutions, the messy documentation, the loss in momentum, and liked a lot of the stuff (especially the tooling and principles) in astro.

Also strongly disliked how political eleventy got.

I just wanted a website, not a an internal debate about what I am potentially being absorbed into. I can vote, and spend money on donations, I don't need to enact change through my tech stack.

Re: Cloudflare acquires Astro

#68
Welp, I'm worried. I like Astro, but maybe it's time to make my own SSG, to not ever end up in the hand of a few big-sharks that consolidate and enshittify everything.

Re: Cloudflare acquires Astro

#69
post #39

> 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 "server client" model suddenly doesn…

IMO it's because the web has a huge diversity of behaviors (in a way that, say, native apps do not) but a monoculture on the development side. React makes sense if you're making Gmail. It doesn't really make sense if you're making a mostly static blog. But because there are more job opportunities in the former (when you consider the wealth of internal web apps out there in the world) all the training courses folks ta…

> Users get by with it.

They would not if they had choice.

Re: Cloudflare acquires Astro

#70

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

> They still don't support inter-island communication Can't you just use standard DOM events for that on the client? This would work even pushing events from React to Vue to Vanilla.

That's what I did, but DX is not great. I would prefer some kind of channel API.
Post reply on HN