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

191–200 of 409 posts

Re: Cloudflare acquires Astro

#191

Post by kevinskii »

nindalf wrote: post #103

I’ve used Astro on Cloudflare for a few years for my personal website (username.com). They’ve both been absolutely fantastic, I can’t say enough good things about both of them. My website has all 100s on PageSpeed/Lighthouse, and that’s because of the performance focus of both Astro and Cloudflare. No credit to me at all. It was mainly because Astro prioritised shipping 0 JS unless it was absolutely necessary and Clo…

Likewise! I built my personal blog with Astro and host on Cloudflare (username.dev), and feel guilty about taking advantage of such excellent software and free tier. Here’s hoping they find a way to take my money soon.

Re: Cloudflare acquires Astro

#192

Post by samtp »

dkhenry wrote: post #95

Astro on Cloudflare workers has been my goto stack for multiple years now. I am very happy with it, and hope this makes the integration stronger. Now we just need Cloudflare to buy one of the DBaaS companies so they have a solid relational offering.

Even just having a better DX/UI around D1 and their other current offerings would be a great start

Re: Cloudflare acquires Astro

#194

Post by pier25 »

__jonas wrote: post #35

I like the idea behind Astro, I've used it for a couple websites here and there. I'm a bit worried about the complexity brought by Astro supporting all these different frameworks through its adapters, and how stable and maintainable those websites will be in the future. For instance: I've been using Astro with Svelte to build static sites with some components that require client-side interactivity. I really like that…

A fix is coming: https://github.com/withastro/astro/pull/15227

Re: Cloudflare acquires Astro

#195

Post by jakubmazanec »

nozzlegear wrote: post #122

I'm a little wary of this. I'd been using Gatsby for my static websites for a long time, until it got eaten up by Netlify and then sunset; I switched over to Astro at that point, but now I'm getting a sense of déjà vu.

Gatsby was sunset because it was a bad framework build on bad decisions [1]. I tried to use it when it was new, and it was immediately obvious that "GraphQL for everything" leads to horrible DX.

[1] https://news.ycombinator.com/item?id=39619110

Re: Cloudflare acquires Astro

#196

Post by jrnichols »

pousada wrote: post #99
jcmfernandes wrote: post #13

Damn. What alternatives does HN recommend?

HTML. Unironically have been migrating my static pages (from Nextjs and Eleventy) to plain HTML and love it. Of course depends on your use case if that is feasible.

Same, and I was starting to feel kind of strange doing anything in html/php in 2026 but then I looked at everything else and realized I'd have to start from scratch again. Plain ol' HTML has worked great.

Re: Cloudflare acquires Astro

#197

Post by ghurtado »

taraindara wrote: post #186
cornholio wrote: post #160

Earlier quoted context omitted.

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

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

I don't see the relation between those two

Re: Cloudflare acquires Astro

#198

Post by hungryhobbit »

mattgreenrocks wrote: post #188
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?

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

Definitely irrational. There are lots of logical reasons to dislike Next (like the fact that they pile new shiny bit on top of new shiny bit without caring about the regular user experience) ... but being mad that it can't run on Vite is silly.

It's like being mad that Rails can't run on Python, or that React can't run on jQuery. Next already has its own build system, so of course it doesn't work with another build system.

Re: Cloudflare acquires Astro

#199

Post by zipy124 »

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.

Sometimes it is cheaper to buy a company than build the internal tool team you might have had to build from scratch anyway. Half acqui-hire, half knowing you've built something on-top of it and want it to stick around.

I also wouldn't be surprised if cloudflare wants to build this into their site-hosting capabilities.

Re: Cloudflare acquires Astro

#200

Post by ghurtado »

Y_Y wrote: post #169
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…

This reads like marketing copy. Maybe it reflects your actual feelings but it's hard to imagine that if you don't write like a human.

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