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

331–340 of 409 posts

Re: Cloudflare acquires Astro

#331

Post by buu700 »

weakfish wrote: post #328
buu700 wrote: post #294

Earlier quoted context omitted.

Here's a trivial example: https://supremecommander.ai . A raw CSS implementation of my blog's logo would have been a pain to build and maintain, but with Astro the code is relatively straightforward JS that becomes pure HTML/CSS at build-time. The other nice thing is that you can throw all kinds of preexisting components from React/whatever into your site, and it will ship zero JS to the client until you explicitly f…

Your website also reloads itself every 4 seconds for me on mobile Firefox

Good to know, thanks! I can't reproduce that on Android (and it's especially weird since the site has almost no JS), but I'll investigate and try to figure it out.

Re: Cloudflare acquires Astro

#332

Post by halfcat »

sureglymop wrote: post #292
__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…

I used it just with web components and pure html/js. Honestly don't even have a need for any framework with it, it's a great ssg like that already.

Interesting. Do you just build web components instead of React/etc, and add the client:load and Astro gives you the static (fast) initial page load, and lazy loading of web components?

Re: Cloudflare acquires Astro

#333

Post by azangru »

pjmlp wrote: post #306
azangru wrote: post #167

Earlier quoted context omitted.

Plain html has two things going against it. First, it doesn't have any provisions for code reuse. So, if you have multiple pages that use the same header, same footer, or same navigation menu, your options are either to copy-paste it (gross), or to build the final html out of smaller pieces, at which point you've reinvented either a static site generator or a web server. Second, if you write long stretches of text, t…

Or I don't know, use WebComponents.

How would this help? You would want your header render on the server, wouldn't you? Not to incur a CLS penalty, right? How does a web component help in this scenario?

Re: Cloudflare acquires Astro

#334

Post by weakfish »

buu700 wrote: post #331
weakfish wrote: post #328

Earlier quoted context omitted.

Your website also reloads itself every 4 seconds for me on mobile Firefox

Good to know, thanks! I can't reproduce that on Android (and it's especially weird since the site has almost no JS), but I'll investigate and try to figure it out.

Np! Hopefully my comment didn’t come off aggressive, meant it to be helpful

Re: Cloudflare acquires Astro

#335

Post by hdra »

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.

I noticed the astro docs has lot of mention of Cloudflare worker as well, is there any reason why you didnt go with Cloudflare pages instead? I’d have guessed pages would be the perfect fit for hosting a rendered astro website

Re: Cloudflare acquires Astro

#336

Post by yusufnb »

gulugawa wrote: post #301
yusufnb wrote: post #229

I have always liked Astro. It also works great with AI tools since its combination of markdown and code. Was able to vibe code a quick blog template and deploy to cloudflare in minutes with an existing headless backend - https://sleekcms-astro-blog.pages.dev/

This is making me even less interested in trying Astro. Websites should not be vibe coded.

The code is vibe-coded. Not the content. Which I think is more important for a blog site.

Re: Cloudflare acquires Astro

#337

Post by rimmontrieu »

This is a great news for Astro. It ticks all the boxes when being used to build heavy content and SEO driven websites. I've been using (Astro + Cloudflare workers/pages) as my go-to stack to build my Java gamedev resources website [1] and gaming portal [2], so far and the experience is very positive. Deploying static files to Cloudflare edges feels natural and frictionless.

Still a bit concerned that it might be too tempting to build an entire website infrastructure around cloudflare, which is a single point of failure. But there is really no better alternatives at the moment. I tried self-hosting but eventually resorted to cloudflare because of bad bots, ai, scrappers kept hammering on my sites.

[1] https://raizensoft.com/tutorials/ [2] https://ookigame.com

Re: Cloudflare acquires Astro

#338

Post by JavierFlores09 »

css_apologist wrote: post #238
arjie wrote: post #166

Very nice to see these dev tools get an exit. e.g. I love `uv` and friends but did consider that perhaps dev tools are just a bad business and then no one will go into making that kind of stuff. Good exits means more of these tools. I have only used Astro for toy stuff but it seemed neat. Congrats to the team. EDIT: To put paid to the sidebar discussion below, yes I meant "for instance, consider `uv`; they might do t…

i'm interpreting this in the reverse if dev tools can only be "monetized" by being bought out, it does not feel sustainable on any level we will see companies attempt to do things like close source these projects, go subscription based, or just straight up drop support there is no incentives for cloudflare to make astro better, or even keep it around same goes with bun, svelte, and i'm sure countless others

Who's to say there's no incentive. Anthropic using Bun internally is plenty incentive to make it better even if for their own use-case. I think it is a bit of a doomer perspective to think anything being bought out means the end of the line for that project. Sure, some things might change depending on the interests of the new owners but that's not to say it'll automatically become bad. Microsoft bought Github and Mojang, they're both doing better than ever for example

Re: Cloudflare acquires Astro

#339

Post by csomar »

everybodyknows wrote: post #272
csomar wrote: post #84

Earlier quoted context omitted.

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.

Following your link, the fault for this appears to lie entirely with Vercel management. Cross fingers that CloudFlare never try similar lock-in games, now that they control Astro?

I don’t think so since they are using the worker model. My guess is that the first class support will go to that. Though they can do lockin differently (kv, queues, etc..)

Re: Cloudflare acquires Astro

#340

Post by mmooss »

mynameisvlad wrote: post #208
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.

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.

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.

Post reply on HN