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

171–180 of 409 posts

Re: Cloudflare acquires Astro

#171

Post by satvikpendem »

woodruffw wrote: post #168
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…

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

Re: Cloudflare acquires Astro

#172

Post by unfunco »

whimsicalism wrote: post #156
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.

cloudflare wants to be vercel

Cloudflare wants to be worth much less?

Re: Cloudflare acquires Astro

#173

Post by satvikpendem »

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.

It does not read like marketing copy to me, what part of talking about draft PRs and framrworks sounds like marketing speak? They're right that CloudFlare having priority access to new Astro features is beneficial for them.

Re: Cloudflare acquires Astro

#174

Post by shimman »

Zanfa wrote: post #165
afavour wrote: post #39

Earlier quoted context omitted.

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…

> React makes sense if you're making Gmail. Except the old Gmail used to be so much faster…

Also the old Gmail never used react...

Re: Cloudflare acquires Astro

#175

Post by epolanski »

chuckadams wrote: post #157
bflesch wrote: post #92

Earlier quoted context omitted.

Cloudflare definitely gets positive PR out of this which makes people forget their CEO's recent meltdown on twitter.

The "meltdown" where he refused to jump to the whims of Italy's football cartel and block whatever addresses they wanted without accountability or review? More meltdowns, please.

A meltdown is a meltdown.

Cloudflare is bound to respect the laws of the countries it operates, and if he disagrees with the process, understandable, that was not the way to express it.

Re: Cloudflare acquires Astro

#176

Post by kelvinjps10 »

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.

Advertise their solution? Now astro can put them into the main deploying option and that's a good way for cloudfare to acquire new customers

Re: Cloudflare acquires Astro

#177

Post by MatthewPhillips »

__jonas wrote: post #119
catoAppreciator wrote: post #87

Earlier quoted context omitted.

Any reason you didn't use alpine for client side interactivity? When I went down the "use a framework plugin in Astro" route, I found it too jarring and reverted to alpine which I found worked well enough.

No, not in particular, I just like Svelte's compilation-based approach, but Alpine definitely looks nice. When the client side interactivity is very contained and small in scope I also quite like just using plain JavaScript without a framework.

Sorry we haven't fixed this issue sooner. In this case it's a complicated CSS issue, but nevertheless I've got a fix I'm working on here:

https://github.com/withastro/astro/pull/15227

Re: Cloudflare acquires Astro

#178

Post by fr3dx »

yawnxyz wrote: post #86

Surprised this isn't in the article, but Cloudflare has been moving all their docs to Astro's Starlight docs framework. I'm guessing this is a way to prioritize features for Cloudflare: > https://blog.cloudflare.com/open-source-all-the-way-down-upg...

It is mentioned in the cloudflare blog post [1]

"At Cloudflare, we use Astro, too — for our developer docs, website, landing pages, and more"

[1] https://blog.cloudflare.com/astro-joins-cloudflare/

Re: Cloudflare acquires Astro

#179

Post by hydroxideOH- »

jcmfernandes wrote: post #13

Damn. What alternatives does HN recommend?

I recently rebuilt my site with Parcel + React Server Components. RSC are designed to solve many of the same problems that Astro does. And Parcel is “just” a bundler and not a framework, so it has less magic and gives you more control.

https://micahcantor.com/blog/rsc-rewrite.html

Re: Cloudflare acquires Astro

#180

Post by brunoarueira »

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.

I had moved out from Gatsby to Astro on my blog/site (username.com), mostly because the enormous dependency hell full of security issues, I know it's just things to generate static files, but it was causing a lot of headaches to upgrade and remove the issues. With Astro, I receive a lot less issues and the maintenance is easier! From my perspective if Cloudflare keep it that way, it'll be a win.
Post reply on HN